A stack trace lacking your source code with all the variables and function names, is like putting together a jigsaw puzzle without a picture for reference. You have all these randomly shaped pieces but no way to know how they fit together. Unless you are fluent in computer, making sense of a JavaScript stack trace with minified code is going to make debugging very difficult. Thankfully, by uploading source maps to Sentry, you can map back to the original source code to make sense of what went wrong.
When developers build and deploy their apps, understanding what’s slow or broken in production is more a necessity than a convenience. With Sentry, developers are able to quickly pinpoint and fix issues that impact their end users or business, and we want every developer to have the best error monitoring in place from the moment they deploy code to production. So we’re partnering with Fly.io to do just that.
Not sure which performance metric to use to measure your application performance? Don’t worry – you’re not alone. With a wide variety of options, the task of choosing the right metric can be daunting. This post will help you decide which metric is right for your monitoring needs by discussing the strengths and limitations of each metric.
With Session Replay tools, you can more easily see what user actions lead to an error. For example, Sentry’s Session Replay is a first class integration with frontend errors that handles this case beautifully. Session Replay records the web browser, which will only show issues if they happen on the user’s webpage browsing session. As a backend developer, I thought it was a great feature, although I didn’t get to use it much.
This is the 25th year of the Open Source movement, and as with any social enterprise there is a constant effort to maintain and at times renegotiate the meaning of terms and the values behind them. Open Source is a child of the Free Software movement. It uncritically inherited its values and philosophy from its parent, but are those still sufficient today?
It was a rainy day in Seattle at KubeCon + CloudNativeCon North America in December 2018 when I first encountered the term ‘OpenTelemetry.’ At that time, I was an active member of a working group focused on developing W3C Trace Context, a standard now extensively employed for context propagation in distributed systems.
During the month of August we dropped heaps of new features across the entire Sentry platform. From identifying user frustration through rage and dead clicks to expanding front end Profiling support, your Sentry Dev Team has skipped their summer vacations (well, kinda…) and been hard at work delivering more capabilities to help you better deal with application errors and performance issues.
If you’re using Sentry for JavaScript error monitoring, you may be familiar with a common challenge: sifting through noisy, low-value errors that hinder identifying high-priority issues for you and your team. Capturing errors in JavaScript browser project can be tricky. Why? Well, it’s not just a single environment.
