victoriametrics

Just to add, VictoriaMetrics covers all 3 signals: - VictoriaMetrics for metrics.

I'm unaware of VictoriaMetrics users who hit PromQL compatibility issues during the migration from Prometheus, Thanos and Mimir to VictoriaMetrics.

I'm the core developer at VictoriaMetrics - you can find this information by clicking my account name here.

Monitoring is VictoriaMetrics + VictoriaLogs + Alloy + Grafana with 16 auto-provisioned dashboards.

And I do use VictoriaMetrics + Grafana on projects for clients, have done so for years now.

Consider migrating to VictoriaMetrics and saving on storage costs and operations costs.

They're using VictoriaMetrics on approx scale of 5 Billion active time series.

VictoriaMetrics is used as a drop-in replacement for Prometheus, Thanos and Mimir.

I was previously leaning torwards VictoriaMetrics and VictoriaTraces (I will need both) but I think that OpenObserve is even simpler.

The main Enterprise feature - high-quality technical support by VictoriaMetrics engineers.

There are plenty of ways to scale Prometheus: - Thanos - Mimir - VictoriaMetrics All of them provide a way to scale monitoring to insane numbers.

We've had success keeping things simple with VictoriaMetrics stack, and avoiding what we perceive as unnecessary complexity in some of the fancier tools/standards.

You end up with 10,000 dashboards and still can't answer "is checkout broken right now?" The open source stack has gotten genuinely viable: Prometheus/VictoriaMetrics for metrics, Grafana for viz, and OpenTelemetry as the collection layer means you're not locked into anyone's agent.