You shouldn’t need a Ph.D. in your APM tool to understand the performance of your application. Sentry’s new approach to application monitoring is focused on being actionable, affordable, and *is actually* built for developers. Learn how we're redefining the future of APM.
How your code performs isn’t a subjective debate. Well, at least not anymore — in the past few months, Sentry has started telling you exactly what’s slow and…
A Sentaur who uses Sentry to build Sentry wanted to know where a specific service associated with an issue was being hosted in our cloud environment. This…
At Sentry, we practice continuous delivery, which means that code can be released as soon as it’s merged into the main branch. This allows us to iterate…
As an open source company that grew out of a side project in 2008 to an application and performance monitoring platform (APM) used by over 3.5 million…
Third-party JavaScript libraries provide developers with the tools they need to build modern web experiences, and a bit of cheatcode at times to not have to…
We’re making Session Replay generally available to all Sentry users. Remove the guesswork from troubleshooting by seeing video-like reproductions of what users experience leading up to and after an error or performance issue. Session Replay supports all web-based platforms.
Recently, we wrote about the demonstrative move to declarative UI. With Jetpack Compose, Android is joining the declarative trends. Jetpack Compose, a new…
A couple months ago, we launched Profiling in alpha for users on Python and Node.js SDKs — today, we’re moving Profiling for Python and Node.js to beta.…
Discover the basics of profiling and its role in application performance. Learn how profiling works, its impact on debugging, and why it’s essential for developers.
This is part 2 of a 2-part series on profiling. If you’re not yet familiar with the what profiling is, check out the first part in our series. - Part 1: What…
Stack traces show us exactly where an exception occurred, but you can still be left wondering: What arguments or state caused the exception to occur? If you can reproduce the issue locally with a debugger attached you’ll have access to these local variables, but with Sentry you can identify the exception location *without* needing to reproduce the issue locally. By including local variables with stack traces, Sentry events become much closer to the full debugging experience.
We’re creating a new way to install and set up Sentry. Starting with Next.js, you’ll be able to set up new Sentry accounts or create new Sentry Next.js…
Do your cron jobs (aka scheduled jobs) ever fail or not run as expected? Scheduled jobs are supposed to be predictable – as the name implies. But as with many…
Taking a look at where mobile app development is headed, and exploring the new declarative approach used by the new native frameworks SwiftUI and Jetpack Compose.
