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.
Sentry developers work ridiculously hard to make sure that every update makes the developer experience better. And, just like you, we use Sentry to monitor…Sentry. While our issues feed seems under control, alerts aren’t popping off, and our releases are all healthy, our experience has taught us the undeniable value of taking a proactive approach to unseen customer-impacting issues.
Profiling is an essential component of a developer’s toolkit for identifying and addressing the thorniest performance bottlenecks. Whether you’re a backend developer looking to cut down cloud infrastructure costs, a frontend developer trying to speed up page load times, or a mobile app developer working to ensure smooth scrolling for users, Sentry Profiling pinpoints hot code paths in your production environment, so you can identify and optimize the slowest parts of your code.
During the past month of July, the Sentry dev team dropped new capabilities to help you better understand, prioritize, and respond to errors and performance problems. From new ways of sorting priority issues to helping you be more proactive in identifying problems earlier in the dev lifecycle, we’ve picked a handful of recent releases to dive into. Plus we’ll highlight a couple of new integrations with our friends at Slack and Atlassian.
Distributed tracing is a powerful technique that allows you to track the flow and timing of requests as they navigate through a system. By linking operations and requests between multiple services, distributed tracing provides valuable insights into system performance and helps identify bottlenecks. In this blog post, we will delve into the benefits of distributed tracing, explore its relevance for various application architectures, and uncover how it operates behind the scenes.
Imagine you start a new hobby — let’s say bike riding. You don’t want to invest a lot in a bike because you’re not sure that you’ll like it. Luckily, you snag a free bike from a friend — it’s clunky, but the price is right. You start out with short rides around your neighborhood and eventually find yourself riding every day, going on longer and longer rides. Your free, heavy bike is holding you back.
Get ready for another round of new releases that will help take your performance and error troubleshooting to the next level. Over the past month of June, we’ve launched a variety of new features that give you more flexibility in managing code coverage, help get to root cause faster, and streamline your everyday usage of Sentry. Here’s the list.
