A trace is the end-to-end journey of one or more connected spans and a span is an operation or “work” taking place on a service. So when it comes to debugging a performance issue, being able to pick out slow spans out of a line up is the fastest way to seeing the root cause and knowing how to solve it. Suspect Spans surfaces a list of spans that correspond to where the most time in a transaction is spent.
In cases, when a crash happens in your Android application, you want more context on what occured before the issue — kind of like following breadcrumbs to the exception. Our SDKs automatically report breadcrumbs for activity lifecycle events, system events, HTTP requests, and many more. Now, Android developers will also see UI events listed as breadcrumbs and get the full picture of what happened without ever having to recreate the issue.
Jay V is one of the founders of Serverless Stack (SST), an open-source framework that makes it easy to build serverless apps. He spends his time trying to figure out what the future of the cloud will look like. And liking memes on Twitter.
The last year has undoubtedly been a challenge for all of us. But humor us one final retrospective as we (happily) leave 2021 in the dust. Our mission remains to help you see what actually matters, solve quicker, and learn continuously about your applications. So here’s what we did this year to make that happen.
Two months ago, we announced our annual investment in open source maintainers, mostly folks whose work we depend on to deliver Sentry to you, plus a few research and hobby projects that our employees put on our radar. Two days ago, six of these maintainers joined us for a one-hour panel called “The Future of Open Source: Is It Sustainable?” I co-hosted with Jessica Lord, Product Manager of GitHub Sponsors.
This is the first part of a blog post series about bytecode transformations on Android. In this part we’ll cover different approaches to bytecode manipulation in Java as well as how to make it work with Android and the Android Gradle plugin. In the next two parts we’ll dive into the actual bytecode, bytecode instructions and how we can modify the bytecode and inject our own instructions, using Room as an example.
Now every developer can customize the performance monitoring charts and data views on the Performance page to see what is most important to them and their team, helping prioritize relevant performance monitoring metrics so they can take action faster. And when you jump back into Sentry Performance, the page is saved right where you left off. Say you’re working on a new release. You can edit your Performance page to include User Misery, Transaction Throughput, and Failure Rate.
We’re delighted to announce that we’ve acquired Specto, a powerful mobile profiling tool from ex-Facebook mobile experts who share our determination for building developer-first performance monitoring products that actually suit the modern dev stack.
At Sentry, we’re always looking for innovative ways to dogfood our product. Over the last year we added Sentry’s error monitoring to our developer environment so that we could better understand the health of it. In this blog post I’m going to touch on how fragile local development environments can be, how we brought observability into what’s happening by introducing Sentry, and what outcomes it has driven for our engineering organization.
For many engineering leaders, measuring their team’s impact can be hard to quantify and a face:palm process, filled with searching through logs and exporting data sets to cobble together a report that most people won’t even look at twice. And let’s be honest, if you wanted to spend time making reports, you wouldn’t have become a developer.
