coroot VS mimir

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

It consists of 6 separate components to run, plus 4 additional optional components [1]. And I don't even count 5 additional caches [2]. How is that "simple and easy"?

[1] https://grafana.com/docs/mimir/latest/references/architectur...

[2] https://github.com/grafana/mimir/blob/9a52522a05f25d6d6bc2e8...

Yes, but also no. The Prometheus ecosystem already has two FOSS time-series databases that are complementary to Prometheus itself. Thanos and Mimir. Not to mention M3db, developed at Uber, and Cortex, then ancestor of Mimir. There's a bunch of others I won't mention as it would take too long.

I used the one in their tutorial.

Grafana Agent can collect and stream data via Prometheus remote write protocol. Then you can either use Prometheus or Mimir. to receive the data at a central location. It depends on how many millions of series you need to collect.

Long term storage all depends on your needs and sophistication. I use Thanos for our system since it has an extremely flexible scaling system. But there is also Grafana Mimir. They're both similar in that they use Prometheus TSDB format as part of the underlying storage. One nice Thanos advantage is that it does do downsampling in addition to being able to store raw metric data for a long time. It will auto-select downsampled data to make requests faster.

Grafana Mimir - scalable storage for Prometheus

Depending on how you want to set things up, you can use Thanos or Mimir to create the single-pane-of-glass view of your data.