The first question is, what is Observe?
The founding of the company was pretty simple. We knew that everybody was trying to move their businesses online, become digital. Every new startup is born in the cloud. And we knew that people were building applications a slightly different way. You have updates and a new code going into production every day. We knew that the environment that those applications were running in was more complex. It was Kubernetes, it was AWS, it was a lot of things that people weren’t familiar with. [Things could go wrong.] Going wrong doesn’t just have to be an outage or something fatal. It could just be the performance starts to slow down. There is an error on the sites. There is an expected behavior. And when those kinds of things happen, the team supporting the application is really challenged to figure out what the heck is going on. ...
These systems have gotten so complex. And so we thought, there’s got to be a way to solve that problem. There has to be a way of looking at all of the data that the applications and the infrastructure emits. There’s got to be a way to figure out what’s going on.
So where does Observe fit in?
Observe really is tackling this emerging segment of the market, which is now called observability, and really looking at it as a data problem. We felt if we could bring the logs into Observe, which is traditionally done with Splunk or Elasticsearch or something like that, and bring that together with the metrics data that’s typically in a Datadog, together with the tracing data, which is maybe typically in AppDynamics or New Relic, if we could bring that into one place, we could make it much easier for folks to figure out what’s going on.
So that really was the founding thesis of the company: Bring all the data together, try and make sense of it, and make it easy for people to figure out what the heck is going on in their application or on their website. So ultimately they can keep customers happy. They could stop the churn. And they can give a great experience.