coroot VS compliance

I'm Peter Zaitsev, co-founder at Coroot. I come from the database world where observability, or monitoring, was crucial for keeping databases running smoothly. But as technology evolves, so do the challenges we face.

Today, many applications are built using microservices architecture, making it harder to pinpoint issues. Developers now have more ownership over the entire environment, but they lack the expertise to navigate intricate infrastructure details. And with the complexity of modern observability systems, crucial components often go unmonitored, leaving blind spots.

That's where Coroot comes in!

We're excited to announce the release of Coroot 1.0 – a simplified observability platform designed to provide actionable insights for modern environments. With Coroot you get:

- Comprehensive Visibility: Coroot covers your entire environment, ensuring no information gaps. Whether you're on Kubernetes, traditional VMs, or cloud services, Coroot has you covered.

- Simple Deployment: We've made deploying Coroot a breeze. Leveraging modern Linux features like eBPF and Netlink, setup requires zero configuration. Coroot also identifies and configures additional components for you.

- Actionable Insights: Coroot prioritizes the most important information, helping you resolve issues up to 80% faster than with legacy solutions.

And the best part? Coroot has open-source version. If you prefer a hosted solution, there is Coroot Cloud, which comes with a free trial and transparent affordable pricing.

While Coroot is already an awesome open-source observability platform, we're not stopping there. We have ambitious plans to automate issue resolution and minimize human intervention.

Got ideas? Let us know on GitHub - https://github.com/coroot/coroot

See detailed overview of Coroot Features - https://coroot.com/overview

Take a look at https://github.com/coroot/coroot (Apache 2.0). It offers plenty of ready-to-use dashboards and inspections

I think ClickHouse is becoming a default storage for observability nowdays: https://clickhouse.com/use-cases/logging-and-metrics

And there are quite a few solutions on top of it.

A couple of examples that seem to be interesting (however I didn't use them in real life):

https://coroot.com/

Landing page: https://coroot.com

Scrape is typically just how people get started and works well for small and medium things, it gets you a long way before you need to consider it.

Prometheus remote_write is what people graduate to, this gets you the rest of the way, and you are correct it's less PITA at scale.

If you're looking for retention your choices are large, there's Cortex (CNCF), Mimir (most Cortex work moved here), Thanos, VictoriaMetrics, TimeScale, Chronosphere, and many others.

All seek to do a similar thing from a distance, they all store metrics (likely from Prometheus) and allow retention and some variety of how to query it (if you want SQL you got it, if you want non-standard functions you go it, if your reads are more important than your writes you got it, if you need a billion active series you got it, etc).

If what you want is "Prometheus but bigger" then the Prometheus project provides a compliance suite that you can run to help you evaluate your options: https://github.com/prometheus/compliance

I work for Grafana Labs, and we have maintainers working for us who have touched Prometheus, Thanos, Cortex and Mimir. Mimir is currently the largest investment we have https://github.com/grafana/mimir and it is 100% compliant with Prometheus (though that is about to be temporarily untrue as Native Histograms is landing in Prometheus soon https://github.com/prometheus/prometheus/milestone/10 and we'll need to add a perfectly compliant support to Mimir to get back to being compliant).

This sounds great. Are you aware that we are launching the Prometheus compliance progam? You might be interested: https://github.com/cncf/prometheus-conformance