Dave Rosenthal

And come to the conference.

So this is like a big deal, like boosting everything. It's going down, man.

So this is like a big deal, like boosting everything. It's going down, man.

Man, man. Wow. I don't know. If you throw a scotch in there.

Man, man. Wow. I don't know. If you throw a scotch in there.

Smoked scotch. Ooh.

Smoked scotch. Ooh.

Would it be a flight, or would you drive?

Would it be a flight, or would you drive?

Oh, I'd probably fly. I'd probably fly through that nearest thing.

Oh, I'd probably fly. I'd probably fly through that nearest thing.

Cool.

Cool.

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.

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.

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 a 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 You don't just have to look at like three different graphs and sort of line them up in time and try to draw your own conclusions.

So if a 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 You don't just have to look at like three different graphs and sort of line them up in time and try to draw your own conclusions.

You can actually like analyze and slice and dice the data and say, hey, what did this metric look like for people with this operating system versus this metric look like for people with this operating system and actually get into those details.