Moving a large-scale metrics pipeline from StatsD to OpenTelemetry / Prometheus
25 points
2 hours ago
| 4 comments
| medium.com
| HN
Full disclosure - I formerly worked for Grafana Labs.

The size of this Grafana Mimir deployment would rank it in the top echelon of customers. The irony is that this may be a $0 revenue user for Grafana Labs.

dig1
1 hour ago
[-]
> The irony is that this may be a $0 revenue user for Grafana Labs.

Why is that ironic? Since Mimir is open-source, $0 revenue users are expected. AFAIK, Grafana Labs relies heavily on go, typescript, and linux, without necessarily being their top financial contributor. They could have kept Mimir proprietary like Splunk, but whether that would have attracted the same level of adoption or community contribution is another matter.

reply
codeduck
33 minutes ago
[-]
> given Prometheus’s widespread adoption and proven reliability in diverse environments.

I have used Prometheus a lot. Reliable is not a word I would associate with it.

reply
hagen1778
24 minutes ago
[-]
What do you use instead of Prometheus?
reply
codeduck
21 minutes ago
[-]
Given a choice, VictoriaMetrics. It has proven itself time and time again at scale, and requires a very low support investment.
reply
awoimbee
43 minutes ago
[-]
Directly emitting metrics using OTLP instead of having the OTel receiver scrape the metrics endpoint is interesting. I never made that move because the Prometheus metrics endpoint works and is so simple, and it's what most projects (eg kubernetes) use.
reply
jameson
43 minutes ago
[-]
Curious why the team choose Grafana Mirmir over VM cluster?
reply