Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
Comparison · Analytics
fellingdater vs OpenObserve
A side-by-side editorial comparison of fellingdater and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
fellingdater vs OpenObserve: at a glance
What is fellingdater?
Went from estimating felling dates to doing the crossdating that produces them.
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
What is OpenObserve?
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.
fellingdater vs OpenObserve: editorial side-by-side
fellingdater
0.0ANALYTICS
Went from estimating felling dates to doing the crossdating that produces them.
◆ Current state
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
◆ Where it's heading
The package has expanded backwards along the workflow. It began at the last step — given dated series, estimate the felling date — and 1.2.0 added the step before it, establishing those dates by crossdating in the first place. Version 1.2.1 is early polish on that new surface: axis control, non-syntactic column names, encoding safety in read_fh(). The direction is a single package covering the chain from raw ring widths to a felling-date estimate.
◆ Prediction
Expect the trs_* family to keep accumulating polish and additional crossdating statistics, since it is barely a year old and 1.2.1 was already fixing its plotting and top_n behaviour. Whether the two halves of the package get unified into one workflow interface is the open question the entries do not answer.
OpenObserve
6.3ANALYTICS
After its largest release, OpenObserve is patching the seams.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to fellingdater and OpenObserve
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 fellingdater or OpenObserve.
silx
silx settles into maintenance a release after its PySide6 migration
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all fellingdater alternatives → · See all OpenObserve alternatives →
Recent activity from fellingdater and OpenObserve
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOpenObservev0.92.2: compactor delay setting and an MCP base-URI fix
- 5d agoOpenObservev0.92.1 brings the MCP server setup page to the OSS build
- 12d agoOpenObservev0.92.0 adds synthetic monitoring, workflows, and AI observability ⚡
- 12d agoOpenObserveRelease candidate 4 backports fixes before the v0.92.0 GA
- 14d agoOpenObserveRC3 adds agent-level filters and parallel zstd compression
- 20d agoOpenObservev0.91.5 patches an RBAC migration and a layout bug
- 4mo agofellingdaterPolish for the crossdating plots and file reader
- 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit ⚡
- 1y agofellingdaterUser-supplied sapwood data works across all functions
- 1y agofellingdaterFixes fd_report() with user-defined sapwood files
- 2y agofellingdaterJOSS paper accepted; citation updated
- 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
Frequently asked questions
What is the difference between fellingdater and OpenObserve?
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.
Is fellingdater better than OpenObserve?
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.
What are the best alternatives to fellingdater?
Top fellingdater alternatives in Analytics are ranked by recent ship velocity. Browse the "fellingdater alternatives" section above for the current picks, or visit /alternatives/fellingdater for the full list with editorial commentary on each.
What are the best alternatives to OpenObserve?
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.