This message was deleted.

1. Transparency 2. Simplicity 3. Security and privacy conscious. 4. Super-fast installation time 5. Availability of core features (all at one place). 6. Addresses the gap between SaaS vendors and open-source software. 7. Backend is hosted inside your infrastructure. What else one needs in an observability tool @Bheem?

Nice. Not being a Debbie downer here trying to understand the differences that's it. I am huge fan and supporter for open source did some nice contributions as well and would like to contribute here as well. Curious How is this different from Elastic APM which is an open source if you deploy in your infrastructure.

@Ankit Nayan and @Pranay might be better able to answer this question.

I haven’t heard back from anyone here - might be overlooked can some one share some insights ?

• @Bheem Elastic APM by virtue of being from Elastic is tightly coupled to using ElasticSearch as the datastore. We are datastore agnostic and provide modular architecture to support new datastores. Currently we support Clickhouse but other relevant dbs can be supported on community demand. • Elastic is not the best DB for unified observability because it was made to search structureless logs whereas metrics (being time series data) and traces are quite structured. • Elastic is primarily used for logs. Hence, Elastic APM is very log focused. They obtain metrics from logs. If you try to run Elastic APM, under the hood you run Elastic search and Kibana which were made for logs. We use OLAP databases which can crunch aggregates from raw data very fast. When the world is moving towards structured logging, I see more users moving to columnar/OLAP databases. In short, faster query + cheaper storage costs.