If you’re a front end developer, there’s a high probability you’ve built (or will build) an image-heavy page. And you’ll need to make it look great by serving high-quality image files. But you’ll also need to prioritize building a high-quality user experience by making sure your Core Web Vitals such as Cumulative Layout Shift and Largest Contentful Paint aren’t negatively affected, which also help with your search engine rankings.
Knowing what issues to hit the snooze button on, or drop everything and push a hotfix for is a common developer dilemma. Similarly to what was discussed in Sleep More; Triage Faster with Sentry, we’ve been collecting and iterating on customer feedback for ways to reduce issue noise and surface high-priority issues faster.
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?
