Heather: So we want to know what’s going on, but knowing what’s going on can be expensive, right? I mean, as you’re getting all this information, and [need to know] how to sort through it, because yeah, not everything is an anomaly. It’s dangerous, right?
Martin: A hundred percent. That’s the other side of the coin. Even if you can pay for the information, it’s too much raw information. Especially for the end users of these tools that are developers that have potentially not operated [them] before. So all of a sudden you put a person who is not very experienced in doing this and you flood them with a lot of data. That’s just a bad combination in terms of how effective someone can be out there. You can imagine that’s why not only does it cost so much, but the outcomes are getting worse. The return on the cost that you put in is actually getting worse at the same time. It’s a pretty bad dynamic the industry is in right now.
Heather: What, what do you see, what do you see as some of the things that Chronosphere is doing in this area? Which of these things really needs attention?
Martin: The two parts of that equation that I was talking about is really where we are focused on Chronosphere. On the cost side, it’s really helping companies deal with the cost and in particular, deal with this huge increase in data. Part of fixing that problem is just making these tools cheaper. Yes, that is part of the solution. But the other part of the solution is there’s just too much data and not all of it is valuable. But the real problem is it’s really hard to determine what is valuable and what isn’t valuable until something happens. When you are producing the data, you don’t really know what’s gonna be valuable or not gonna be valuable.
Because of that, we actually created not just a product and a feature set for it. We actually created a vendor neutral framework for how teams should think about this. We call it the Observability Data Optimization Cycle. It’s a bit of a mouthful [but] if you want to find information about it, you can find it on our website. But essentially, it’s taking a lot of the concepts of a FinOps function, a function that has gotten good at understanding the financial impact and optimizing it, [then] taking a lot of those concepts and applying it to observability. So you can imagine the first thing you need is probably centralized governance and, and a way to create budgets for individual teams or departments there.
Then you need a way to actually measure the cost, like how much observability data is each team using? It’s not just the company [overall] but who’s using it, right? Then [you] need all of the utilization data, like how is this data being used? What parts of it are useful? [Then] sort of assign value to how much you are paying for it. You ideally need the tools that can match the value and the cost, because it’s not just about dropping the data on the ground, because that’s actually a bad outcome. You really want to perhaps optimize all of your data, thus that you can get the value out of it, but without paying the whole cost. So we created this framework for companies to think about it and really apply a lot of the FinOps concepts to the observability space.
And then, of course, in the product, there’s a whole feature set that goes and does all of these things for you. If you want an out of the box product, we obviously have that. So that’s what we are doing to solve the cost problem. On the other hand, [we have] a few announcements that we have coming up in the next few months that really focus on making the experience and the tooling much more simple for the everyday developer. This where they are being flooded with data. And what they really want is access to insights — and just insights — contextualized presented to them. That’s what a developer really wants. They don’t actually wanna wade through all of the raw data.
Things that I’ll say what we’re gonna be announcing pretty soon. I don’t wanna ruin a surprise, but, they’re coming out soon and focused on that part of the problem. This is really, you know, for Chronosphere, this is the problem in the industry we have to solve: The cost problem and we have to make these tools more effective. It sort of gets the ROI back in balance for companies out there.