John Gallagher

and the reverse is not true like you can't take that event based kind of mindset into metrics because metrics is just that aggregation right so um but i have like recently i've been doing a lot of queries in our rails app and i've been going to we use new relic sorry we use datadog at work and i've been going to datadog's tracing um interface

and the reverse is not true like you can't take that event based kind of mindset into metrics because metrics is just that aggregation right so um but i have like recently i've been doing a lot of queries in our rails app and i've been going to we use new relic sorry we use datadog at work and i've been going to datadog's tracing um interface

and really trying to answer my questions there instead of in logging. So we have both tracing and logging. Our tracing is hobbled a little bit, just purely because of cost reasons. And our logging is not so hobbled. So are the standards heading in the right direction? Yes, but it's going to take a really long time to get there is my short answer.

and really trying to answer my questions there instead of in logging. So we have both tracing and logging. Our tracing is hobbled a little bit, just purely because of cost reasons. And our logging is not so hobbled. So are the standards heading in the right direction? Yes, but it's going to take a really long time to get there is my short answer.

There is a lot of different ways of going about tracing. The most promising, as we all know, is open telemetry. But, I mean, I read some pretty harsh critiques of open telemetry. There's kind of a topic that generally divides people. If you don't know anything about open telemetry, it sounds an absolute utopia. And I got really excited when I started researching into it.

There is a lot of different ways of going about tracing. The most promising, as we all know, is open telemetry. But, I mean, I read some pretty harsh critiques of open telemetry. There's kind of a topic that generally divides people. If you don't know anything about open telemetry, it sounds an absolute utopia. And I got really excited when I started researching into it.

The more you dig into it, the more you realize... how much complexity there is to resolve and how many challenges that project faces in order to resolve them. And so, I mean, what it's trying to resolve is 30, maybe 40 years, possibly even more, of legacy software, right? Because that's how long logging has been around.

The more you dig into it, the more you realize... how much complexity there is to resolve and how many challenges that project faces in order to resolve them. And so, I mean, what it's trying to resolve is 30, maybe 40 years, possibly even more, of legacy software, right? Because that's how long logging has been around.

And they're trying to aggregate all of that into one single standard good look. It's a very, very difficult problem to solve. And they're doing an incredible job. But it's very, very difficult. So they have open telemetry is where I'd start with the answer to your question. Open telemetry is 100% the future. I've not seen anything that rivals it.

And they're trying to aggregate all of that into one single standard good look. It's a very, very difficult problem to solve. And they're doing an incredible job. But it's very, very difficult. So they have open telemetry is where I'd start with the answer to your question. Open telemetry is 100% the future. I've not seen anything that rivals it.

And open tracing, I believe, came first and then evolved into open telemetry, from my understanding. Apologies if I've got that slightly wrong. And so, yeah, I think there's a few options if you're in Ruby. None of which are ideal. So the OpenTelemetry client in Ruby is not ready for primetime. It's quite behind the current standards in OpenTelemetry.

And open tracing, I believe, came first and then evolved into open telemetry, from my understanding. Apologies if I've got that slightly wrong. And so, yeah, I think there's a few options if you're in Ruby. None of which are ideal. So the OpenTelemetry client in Ruby is not ready for primetime. It's quite behind the current standards in OpenTelemetry.

It doesn't obey any of the latest semantic standards, for example. I have played around with it in an example project. And when it's working, it's absolutely incredible. It's next level brilliant. There are a few problems with it. It's extremely slow. So I tried to use tracing on our test suite at work using this open telemetry tracing.

It doesn't obey any of the latest semantic standards, for example. I have played around with it in an example project. And when it's working, it's absolutely incredible. It's next level brilliant. There are a few problems with it. It's extremely slow. So I tried to use tracing on our test suite at work using this open telemetry tracing.

And it just, it's like, I can't remember the numbers, but it really slowed down our test suite to the point where it really just wasn't practical to use because we were trying to measure the performance of the test suite. So, you know,

And it just, it's like, I can't remember the numbers, but it really slowed down our test suite to the point where it really just wasn't practical to use because we were trying to measure the performance of the test suite. So, you know,

um i could have been doing something stupid there it's very possible that i just wasn't using it the right way so sorry open slam machine folks if i've i got i know um i think a lady is called kaylee who is from new relic and she and um I'm so sorry, the names escape me. But there's a whole bunch of people in the Ruby space who are working really hard on OpenTelemetry.

um i could have been doing something stupid there it's very possible that i just wasn't using it the right way so sorry open slam machine folks if i've i got i know um i think a lady is called kaylee who is from new relic and she and um I'm so sorry, the names escape me. But there's a whole bunch of people in the Ruby space who are working really hard on OpenTelemetry.

But it's just that the OpenTelemetry project is moving so fast, that's the other problem. So that's option number one, OpenTelemetry. You could maybe fork it and tweak it yourself. The second option and what we use at work is, because we're using Datadog, we use Datadog's tracing tool, which is pretty good. But then even with tracing or logging, I feel like we're kind of,

But it's just that the OpenTelemetry project is moving so fast, that's the other problem. So that's option number one, OpenTelemetry. You could maybe fork it and tweak it yourself. The second option and what we use at work is, because we're using Datadog, we use Datadog's tracing tool, which is pretty good. But then even with tracing or logging, I feel like we're kind of,