textplot
A bnosac plotting utility in maintenance mode, shipping once every few years
A side-by-side editorial comparison of etn and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
etn stopped being an RStudio-server package and became something you can run anywhere.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
After the 836-commit 0.92 release, OpenObserve is quietly moving its MCP server into the free tier
OpenObserve is in the settle-down phase after v0.92.0, the largest release the project has shipped, which added synthetic monitoring, Workflows v1, an expanded AI observability set, per-group and per-series alerting with SLOs, and moved Vortex and the MCP server into open source. The v0.92.1 patch that followed is small but pointed: the MCP Server setup page now renders on the OSS build, and an alerts bug where the HAVING clause was typed from the column rather than the aggregate is fixed. The 0.91 line continues to receive backported fixes in parallel.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
Two arcs run in parallel: widening access, and making room for non-acoustic data. The access work has been deliberate — an API-backed beta in 2024, then a stable release that picks the transport automatically and checks that a local etnservice install matches the deployed one, because the same query returning different results by transport would be worse than requiring the server. The Darwin Core export added in 2.1.0 points the same outward direction, moving data to OBIS and GBIF instead of keeping it in the ETN silo.
The cpod scope named in the 2.0.0 notes is the most likely next addition, now that the naming and the API transport are both in place to carry it.
OpenObserve is in the settle-down phase after v0.92.0, the largest release the project has shipped, which added synthetic monitoring, Workflows v1, an expanded AI observability set, per-group and per-series alerting with SLOs, and moved Vortex and the MCP server into open source. The v0.92.1 patch that followed is small but pointed: the MCP Server setup page now renders on the OSS build, and an alerts bug where the HAVING clause was typed from the column rather than the aggregate is fixed. The 0.91 line continues to receive backported fixes in parallel.
The MCP thread is the one to watch. Open-sourcing the server in 0.92.0 was the architectural move; serving its setup page on the OSS build a week later is what makes it reachable without an enterprise license. That points at agent clients as a first-class consumption path rather than an enterprise upsell, which is a different distribution bet than the synthetic-monitoring and Workflows surfaces that headlined the same release. Everything else in this window is stabilization — RC backports, memtable rotation, RBAC migrations — consistent with a project digesting a release that spanned two repositories and a large-scale crate reorganization.
Expect a run of 0.92.x patches concentrated on the three new surfaces, since synthetic monitoring, Workflows and eval scheduling all shipped at once with limited production exposure. The alerts fix suggests the aggregation path is a likely source of further corrections.
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 etn or OpenObserve.
A bnosac plotting utility in maintenance mode, shipping once every few years
An epidemic-onset detector that now brackets the whole season, not just its start
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
See all etn 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 etn alternatives in Analytics are ranked by recent ship velocity. Browse the "etn alternatives" section above for the current picks, or visit /alternatives/etn-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.