2024-11-07
1 小时 45 分钟The hallway track at All Things Open 2024 — features Carl George, Principal Software Engineer at Red Hat for a discussion on the state of open source enterprise linux and RHEL (Red Hat Enterprise Linux), Max Howell, creator of Homebrew and tea.xyz which offers rewards and recognition to open source maintainers, and Chad Whitacre, Head of Open Source at Sentry about the launch of Open Source Pledge and their plans to helps businesses and orgs to do the right thing and support open source.
Okay, friends, this is the change log and we're going back to the hallway track at All Things Open 2024 in Raleigh, North Carolina.
This episode features Carl George, principal software engineer at Red Hat.
For discussion on the state of Open Source Enterprise Linux and rhel, better known as Red Hat Enterprise Linux.
We talked to Max Howe, creator of Homebrew and the T protoc at T xyz, which offers rewards and recognition to open source maintainers.
And last we talked to Chad Whitaker, head of Open Source at Sentry, about the launch of Open Source Pledge and their plans to help businesses and orgs do the right thing and support Open Source.
A massive thank you to our friends@flyio that is the home of Change Law dot com.
Deploy your app in five minutes at fly.
Okay, let's do this.
What's up, friends?
I'm here with Dave Rosenthal, CTO of Sentry.
So Dave, when I look at Sentry, I see you driving towards full application health error monitoring, where things began, session replay, being able to replay a view of the interface a user had going on when they experienced an issue with full tracing, full data.
The advancements you're making with tracing and profiling, cron monitoring, co coverage, user feedback and just tons of integrations give me a glimpse into the inevitable future.
What are you driving towards?
Yeah, one of the things that we're seeing is that in the past people had separate systems where they had like logs on servers, written files.
They were maybe sending some metrics to Datadog or something like that, or some other system they were monitoring for errors with some product.
Maybe it was Sentry.
But more and more what we see is people want all of these sources of telemetry logically tied together somehow.
And that's really what we're pursuing at Sentry now.
We have this concept of a trace id, which is kind of a key that ties together all of the pieces of data that are associated with the user action.
So if user loads a web page, we want to tie together all the server requests that happened, any errors that happened, any metrics that were collected, and what that allows on the back end.