Valentino Stoll

But once you start to abstract the ideas and use cases and how people are actually using the thing that you've built, you can definitely isolate what it is that you actually care about. And I think you're right. That is kind of the whole importance of observability.

But once you start to abstract the ideas and use cases and how people are actually using the thing that you've built, you can definitely isolate what it is that you actually care about. And I think you're right. That is kind of the whole importance of observability.

is is identifying that use case and exposing what what you actually care about uh as far as all these things that are because i mean you know there's http logs there's like also all kinds of logs and information available that's just like emitting all the time like how do you know and identify you know which are really important uh and i i think it just depends right like

is is identifying that use case and exposing what what you actually care about uh as far as all these things that are because i mean you know there's http logs there's like also all kinds of logs and information available that's just like emitting all the time like how do you know and identify you know which are really important uh and i i think it just depends right like

What are you yeah, what are you trying to capture? So it's a it's a great like stepwise way to just like start to figure that out. Right. Because, yeah, I guess depending on your role and depending on what, you know, your responsibilities are, that could change and that could be different. And your observability needs will change with that. So identifying that is probably most important, I think.

What are you yeah, what are you trying to capture? So it's a it's a great like stepwise way to just like start to figure that out. Right. Because, yeah, I guess depending on your role and depending on what, you know, your responsibilities are, that could change and that could be different. And your observability needs will change with that. So identifying that is probably most important, I think.

And I'm all also like, you know, let's not just add New Relic to every app that we deploy. Or, you know, is Bugsnag even needed for every app? Like, these are questions that I ask myself, too. Like, what value are you getting from all these auxiliary services that give you the observability into, like, just blanket things? Yeah.

And I'm all also like, you know, let's not just add New Relic to every app that we deploy. Or, you know, is Bugsnag even needed for every app? Like, these are questions that I ask myself, too. Like, what value are you getting from all these auxiliary services that give you the observability into, like, just blanket things? Yeah.

At what point do you stop that kind of mentality and be like, every Rails app should at least be able to get insight into the logs so that you can see what the application is doing. How long do you capture that? What kind of time frame? Do you have any default standards where you're like, well, I know that I'm going to need to look at this at some point in the application cycle.

At what point do you stop that kind of mentality and be like, every Rails app should at least be able to get insight into the logs so that you can see what the application is doing. How long do you capture that? What kind of time frame? Do you have any default standards where you're like, well, I know that I'm going to need to look at this at some point in the application cycle.

What are your defaults?

What are your defaults?

Yeah, you mentioned kind of some key pieces I always think of with observability in general, which is like separating the pieces into their own puzzle, right? Like we have logs, which are kind of just like our data. And then we have individual metrics that we're like snapshotting the logs for particular segments like traffic or number of people using it, like the number of jobs that are running.

Yeah, you mentioned kind of some key pieces I always think of with observability in general, which is like separating the pieces into their own puzzle, right? Like we have logs, which are kind of just like our data. And then we have individual metrics that we're like snapshotting the logs for particular segments like traffic or number of people using it, like the number of jobs that are running.

And then there are traces, which we could dig into next, because I have a lot of love for all of the standards that are coming out of this with open tracing and things like that. I'd love to dig in there. But also like alerting, like, you know, how does anybody know that there's ever a problem?

And then there are traces, which we could dig into next, because I have a lot of love for all of the standards that are coming out of this with open tracing and things like that. I'd love to dig in there. But also like alerting, like, you know, how does anybody know that there's ever a problem?

Yeah, I mean, and I love, I love like thinking about it in these separate groups and categories, because I think it also helps to think about like the overarching theme, which is like getting insight, but also like, getting meaningful insight.

Yeah, I mean, and I love, I love like thinking about it in these separate groups and categories, because I think it also helps to think about like the overarching theme, which is like getting insight, but also like, getting meaningful insight.

And like when you want really like the only the only reason anybody ever cares about observability anyway is like when something goes wrong or something is problematic that causes something to go wrong. And you want to either catch it early or, you know, try and remediate. And so like.

And like when you want really like the only the only reason anybody ever cares about observability anyway is like when something goes wrong or something is problematic that causes something to go wrong. And you want to either catch it early or, you know, try and remediate. And so like.