OpenMetadata
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
A side-by-side editorial comparison of Grafana Mimir and Grafana Loki — release velocity, themes, recent moves, and the top alternatives to consider.
Mimir's feed is weekly chart bot noise; the 3.2 RC is where the breaking changes hide.
Almost every entry in this window is an identical bot-generated Helm chart release — byte-for-byte the same body across seven tags. The one substantive release is the 3.2.0 RC, whose notes run past the feed's truncation point: continued Mimir Query Engine optimisation, native histogram support in more operators, per-tenant cost attribution trackers, and a tenant-fair compute worker pool on the ingester. Buried in its changelog are changes operators must act on — the embedded per-tenant Alertmanager web UI is gone, credential-bearing headers are now rejected at startup, and querier/store-gateway traffic requires coming from 3.1.
Loki 4.0 reaches RC3 and narrows S3 storage classes to Standard and Standard-IA.
Loki 4.0 is moving through release candidates. RC1's notes list the breaking changes: the V2 query engine unplugged, Simple Scalable Deployment targets and old /api/prom endpoints removed, protobuf as the default frontend encoding, and several deprecated settings and metrics dropped. RC2 removed every index backend but TSDB, and RC3 adds one more break, limiting S3 storage classes to STANDARD and STANDARD_IA, plus a compactor delete fix.
Almost every entry in this window is an identical bot-generated Helm chart release — byte-for-byte the same body across seven tags. The one substantive release is the 3.2.0 RC, whose notes run past the feed's truncation point: continued Mimir Query Engine optimisation, native histogram support in more operators, per-tenant cost attribution trackers, and a tenant-fair compute worker pool on the ingester. Buried in its changelog are changes operators must act on — the embedded per-tenant Alertmanager web UI is gone, credential-bearing headers are now rejected at startup, and querier/store-gateway traffic requires coming from 3.1.
Mimir is deepening the query path rather than widening the product: most of 3.2 is MQE work, subquery spin-off, caching and elimination passes, largely behind experimental flags. The operational surface is growing in parallel — Kafka producer controls, mimirtool and kafkatool subcommands, SigV4 for shared API clients. The chart is versioned and released independently on a weekly bot cadence, which is why the feed reads as empty even in an active month.
The experimental MQE flags that landed in 3.2 are the ones to watch for promotion to default in 3.3, particularly subquery spin-off and scalar common subexpression elimination. Whether a 3.2.0 final follows this RC is not visible in the feed — only the RC has been published here.
Loki 4.0 is moving through release candidates. RC1's notes list the breaking changes: the V2 query engine unplugged, Simple Scalable Deployment targets and old /api/prom endpoints removed, protobuf as the default frontend encoding, and several deprecated settings and metrics dropped. RC2 removed every index backend but TSDB, and RC3 adds one more break, limiting S3 storage classes to STANDARD and STANDARD_IA, plus a compactor delete fix.
Each candidate trims a bit more legacy surface, so 4.0 is a cleanup major that pushes installs onto TSDB and the microservices or single-binary layouts. The Operator had prepared this path since 0.11 and 0.12.
Expect a few more RCs with small breaking changes, then 4.0.0 GA and an Operator release that drops the removed schemas.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Grafana Mimir or Grafana Loki.
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
Dovetail lets admins choose which connectors members can plug into the workspace.
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
OpenHouse adds time-zone-aware retention and per-database table caps.
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
See all Grafana Mimir alternatives → · See all Grafana Loki alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — breaking-changes — within Analytics. Grafana Loki is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Grafana Loki is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Grafana Mimir alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Mimir alternatives" section above for the current picks, or visit /alternatives/grafana-mimir for the full list with editorial commentary on each.
Top Grafana Loki alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Loki alternatives" section above for the current picks, or visit /alternatives/loki for the full list with editorial commentary on each.