2024-09-13
1 小时 25 分钟Jerod & Adam share our Zulip first impressions, react to Elasticsearch going open source (again), discuss Christian Hollinger's blog post on why he still self-hosts & answer a listener question: how do we produce podcasts?
Welcome to Changelog and Friends, a weekly talk show about how we podcast.
Special thanks to our partners at Fly IO.
Over 3 million apps have launched on Fly, including ours.
And you can too, in five minutes or less, learn how at Fly IO.
Okay, let's talk.
Hey, friends, I'm here with Dave Rosenthal, CTO of Sentry.
So, Dave, I know lots of developers know about Sentry, know about the platform, because, hey, we use Sentry and we love Sentry.
And I know tracing is one of the next big frontiers for Sentry.
Why add tracing to the platform?
Why tracing and why now?
When we first launched the ability to collect tracing data, we were really emphasizing the performance aspect of that, the kind of application performance monitoring aspect, you know, because you have these things that are spans that measure how long something takes.
And so the natural thing is to try to graph their durations and think about their durations and, you know, warn somebody if the durations are getting too long.
But what we've realized is that the performance stuff ends up being just a bunch of gauges to look at, and it's not super actionable.
Sentry is all about this notion of debugability and actually making it easier to fix the problem, not just sort of giving you more gauges.
A lot of what we're trying to do now is focus a little bit less on the sort of just the performance monitoring side of things and turn tracing into a tool that actually aids.
The debug ability of problems.
I love it.
Okay, so they mean it when they say code breaks.
Fix it faster.
With Sentry, more than 100,000 growing teams use Sentry to find problems fast.