Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of cholera and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
John Snow's 1854 cholera map is being rebuilt on real geographic coordinates.
cholera packages the Broad Street cholera outbreak data with tools to recompute pump neighbourhoods by Voronoi and walking distance. The last two releases carried the dataset from Snow's original plate coordinates onto georeferenced longitude and latitude, exposed through a latlong = TRUE argument on most functions. Function naming and plotting APIs are being tidied at the same pace.
After its largest release, OpenObserve is patching the seams.
v0.92.0 landed on 7 August with 836 commits and three new product surfaces - synthetic monitoring, Workflows v1, and an expanded AI observability set - after a long RC series. The two releases since are small: v0.92.1 fixed alert HAVING clause typing and put the MCP server setup page on the OSS build, and v0.92.2 adds a compactor delay setting and backports an MCP 404 fix for deployments running under a base URI. The 0.91 line is still receiving its own backports.
cholera packages the Broad Street cholera outbreak data with tools to recompute pump neighbourhoods by Voronoi and walking distance. The last two releases carried the dataset from Snow's original plate coordinates onto georeferenced longitude and latitude, exposed through a latlong = TRUE argument on most functions. Function naming and plotting APIs are being tidied at the same pace.
The direction is clear and sustained: convert a historical, self-referential coordinate system into one that interoperates with modern GIS. Each release extends latlong coverage to more datasets — pumps, roads, landmarks, and now the plague pit and map frame — while archiving the older prototypes. Parallelisation and the walking-distance solver were reworked along the way to keep the heavier computations usable.
Remaining non-georeferenced pieces and the archived latlong prototypes are the obvious next targets, alongside continued consolidation of the add*()/plot*() function pairs.
v0.92.0 landed on 7 August with 836 commits and three new product surfaces - synthetic monitoring, Workflows v1, and an expanded AI observability set - after a long RC series. The two releases since are small: v0.92.1 fixed alert HAVING clause typing and put the MCP server setup page on the OSS build, and v0.92.2 adds a compactor delay setting and backports an MCP 404 fix for deployments running under a base URI. The 0.91 line is still receiving its own backports.
OpenObserve is trying to become the whole monitoring stack rather than the storage layer under one. Synthetic checks, incident workflows, and SLO measurement each replace a separate tool, and incident ingestion from external alert sources hedges the migration path for teams that cannot switch all at once. The MCP work running alongside - open sourced, then given a setup page in the OSS build, then fixed for base-URI deployments - shows the same data being aimed at agent clients rather than dashboards.
The post-GA patches are still landing on the new surfaces, so expect another 0.92.x before feature work resumes - most likely hardening synthetic monitoring and Workflows, which are the two least-exercised additions.
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 cholera or OpenObserve.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all cholera alternatives → · See all OpenObserve 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 cholera alternatives in Analytics are ranked by recent ship velocity. Browse the "cholera alternatives" section above for the current picks, or visit /alternatives/cholera-r for the full list with editorial commentary on each.
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.