So, I've been using Thanos to receive and store my prometheus metrics long term in a self hosted S3 bucket. Thanos also acts as a datasource for my dashboards in Grafana, and provides a Ruler, which evaluates alerting rules against my metrics and forwards them to my alertmanager. It's ok. It's certainly got it's downsides, which I can go into later, but I've thinking... what about Mimir?

How do you all feel about Grafana's Mimir (source on GitHub)? It's AGPL and seems to literally be a replacement of Thanos, which is Apache 2.0.

Thanos description from their website:

Open source, highly available Prometheus setup with long term storage capabilities.

Mimir description from their website:

...open source software project that provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus and OpenTelemetry metrics.
Both with work with alloy and prometheus alike. Both require you to configure initially confusing hashrings and replication parameters. Both have a bunch of large companies adopting them, so... now I feel conflicted. Should I try mimir? Poll in reply.

#thanos #prometheus #alloy #grafana #observability #monitoring #kubernetes #k8s #foss #sre

If you've tried both Thanos and Mimir, which do you prefer? Feel free to comment why below 

#thanos #prometheus #alloy #grafanaAlloy #grafana #observability #monitoring #kubernetes #k8s #foss #sre #mimir #grafanaMimir

Thanos
55.6%
Mimir AKA Grafana Mimir
44.4%
Poll ended at .
@jessebot I don't miss Thanos, not even slightly. While the slight impedances with Google Managed Prometheus are a PITA (eg the slightly different CRDs and messy-to-GitOps OperatorConfig stuff), the details that federation and aggregation across projects is just a few clicks or a trivial Terraform stanza away, and you automatically get 2 years of metric retention with no fuss is pretty compelling.
@jcl To clarify, are you using Mimir? I do not want to use a managed service at this time.
@jessebot Nope, just a happy GMP user.