Aim
An experiment tracker grinding on storage performance — and quiet for over a year.
A side-by-side editorial comparison of OpenObserve and Zipkin — release velocity, themes, recent moves, and the top alternatives to consider.
One release turns a telemetry store into synthetics, workflows, and AI observability.
v0.92.0 landed today after four release candidates, spanning 836 commits across the OSS and enterprise repositories. It adds three surfaces the product did not have — synthetic monitoring with private locations and agents, Workflows v1 tied to incidents, and an expanded AI observability set covering trace and session evaluations, an eval scheduler, organization AI credits, and an agent/service graph. Running alongside it, a 0.91.x maintenance branch has been taking small backported fixes on its own cadence.
Zipkin's last release was January 2025 — a dependency bump, and then nothing.
The recent history is three consecutive maintenance releases whose entire content is dependency and base-image updates: 3.4.3 aligned Maven versions with the Docker images, 3.4.2 and 3.4.1 moved Spring Boot, Netty, Micrometer, Armeria, Alpine and the JRE forward to clear CVEs. The last release carrying a feature was 3.4 in May 2024, which added OpenSearch v2 as a storage backend using the existing ES_-prefixed environment variables.
v0.92.0 landed today after four release candidates, spanning 836 commits across the OSS and enterprise repositories. It adds three surfaces the product did not have — synthetic monitoring with private locations and agents, Workflows v1 tied to incidents, and an expanded AI observability set covering trace and session evaluations, an eval scheduler, organization AI credits, and an agent/service graph. Running alongside it, a 0.91.x maintenance branch has been taking small backported fixes on its own cadence.
Scope is moving outward from storing and querying telemetry toward acting on it: alerting gained per-group and per-series rules with SLO measurement, incidents can be ingested from external alert sources, and Workflows connects automation to them. The second axis is observing AI systems rather than merely serving them, with evaluations and an agent graph now first-class. Moving Vortex and the MCP server into open source, the latter on the 2026-07-28 spec with OAuth 2.0 sign-in, points the same platform at agent clients as consumers of its data.
Expect a 0.92.x patch train within days — each of the last two GA releases drew several backport-only point releases — concentrated on the newly opened surfaces. The crate modularization noted in the release also makes a period of build and packaging fixes likely.
The recent history is three consecutive maintenance releases whose entire content is dependency and base-image updates: 3.4.3 aligned Maven versions with the Docker images, 3.4.2 and 3.4.1 moved Spring Boot, Netty, Micrometer, Armeria, Alpine and the JRE forward to clear CVEs. The last release carrying a feature was 3.4 in May 2024, which added OpenSearch v2 as a storage backend using the existing ES_-prefixed environment variables.
This is a project in preservation rather than development. The pattern across the window — feature in May 2024, then three releases of purely defensive dependency work, then silence since January 2025 — describes a mature tracing server being kept safe to run rather than extended. The distributed-tracing work that would once have landed here now largely happens in OpenTelemetry, which Zipkin interoperates with rather than competes against.
The feed has produced nothing for nineteen months, so the honest read is that no next release is scheduled. If one comes, the shape of the last three says it will be another dependency and base-image refresh rather than new capability.
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 OpenObserve or Zipkin.
An experiment tracker grinding on storage performance — and quiet for over a year.
Every Glances release this year has carried CVE fixes — the monitoring tool is being audited in public.
Chord rebuilt Copilot, renamed it, and let it start building the audiences it used to describe
Citus is in maintenance mode across four branches, with the feature work invisible from the feed.
A deprecation sweep and hive-partition join rewrites, shipped on two trains at once.
ServerMap rebuilt and application names finally long enough to describe a service.
See all OpenObserve alternatives → · See all Zipkin alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenObserve is currently shipping more aggressively (velocity 6.3 vs 0.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. OpenObserve is currently shipping more aggressively (velocity 6.3 vs 0.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 OpenObserve alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenObserve alternatives" section above for the current picks, or visit /alternatives/openobserve for the full list with editorial commentary on each.
Top Zipkin alternatives in Analytics are ranked by recent ship velocity. Browse the "Zipkin alternatives" section above for the current picks, or visit /alternatives/zipkin for the full list with editorial commentary on each.