Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Pricing

Valentino Stoll

👤 Person
700 total appearances

Appearances Over Time

Podcast Appearances

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Where do you find like I mean, background jobs are like kind of like I feel like the first instance where people realize like, oh, like we need to start looking at, you know, what it's doing. Right. Like you start throwing stuff in the background. You're like, OK, great. Like it's doing the work.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Where do you find like I mean, background jobs are like kind of like I feel like the first instance where people realize like, oh, like we need to start looking at, you know, what it's doing. Right. Like you start throwing stuff in the background. You're like, OK, great. Like it's doing the work.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Uh, and then you don't maybe realize if you're on the same node, like, well, those, you know, slow requests can block the web requests. Uh, right. And then, okay, well, if you split those up, finally you got that resolved, but then, okay, well, one problematic, you know, job can back up a queue that it's on. Uh, you know, like where do you, uh,

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Uh, and then you don't maybe realize if you're on the same node, like, well, those, you know, slow requests can block the web requests. Uh, right. And then, okay, well, if you split those up, finally you got that resolved, but then, okay, well, one problematic, you know, job can back up a queue that it's on. Uh, you know, like where do you, uh,

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

To me, like the background processing aspect is like why we have tracing to begin with, because it does like it's concurrency. Right. So it's like that's where everybody like ends up hitting their pitfalls is as soon as you start doing things like all at once, like and thinking, oh, like we just throw it in the background and like process things as they come.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

To me, like the background processing aspect is like why we have tracing to begin with, because it does like it's concurrency. Right. So it's like that's where everybody like ends up hitting their pitfalls is as soon as you start doing things like all at once, like and thinking, oh, like we just throw it in the background and like process things as they come.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

And as things start to scale, it causes more problems as you try and figure out timing and stuff like that. Where do you find the most important pieces of making sure that you are capturing the right segments and the right flows in that process?

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

And as things start to scale, it causes more problems as you try and figure out timing and stuff like that. Where do you find the most important pieces of making sure that you are capturing the right segments and the right flows in that process?

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Yeah, I mean, it's more of like an open question. I guess like when trying to think about like one of my biggest debugging pitfalls is like trying to like reconstruct the state of what happened when something went wrong. It's like I feel like that's like one of the most typical things. It's like, OK, something happened. Like, well, like it's the data has changed since something had happened.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Yeah, I mean, it's more of like an open question. I guess like when trying to think about like one of my biggest debugging pitfalls is like trying to like reconstruct the state of what happened when something went wrong. It's like I feel like that's like one of the most typical things. It's like, OK, something happened. Like, well, like it's the data has changed since something had happened.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Maybe the change resolved the issue. But like, you know, trying to figure out what that is and going running through those questions. Right. Like. How do you think about like reconstructing data or reconstructing the state of an issue? Like, is that not the right way to go about it? Or do you try and like do something else?

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Maybe the change resolved the issue. But like, you know, trying to figure out what that is and going running through those questions. Right. Like. How do you think about like reconstructing data or reconstructing the state of an issue? Like, is that not the right way to go about it? Or do you try and like do something else?

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Okay, so there'll be a lot of- Wait, what are the three pillars?

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Okay, so there'll be a lot of- Wait, what are the three pillars?

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Okay.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

Okay.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

I think that you're making some great points of capturing the transactional like user information or user's actions. Yes.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

I think that you're making some great points of capturing the transactional like user information or user's actions. Yes.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

I guess I do have like maybe some specific instances where metrics alone can help like identify things. And that's more where it's like the granular metrics are the things that you're actually looking like care about. Right.

Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656

I guess I do have like maybe some specific instances where metrics alone can help like identify things. And that's more where it's like the granular metrics are the things that you're actually looking like care about. Right.