ManageEngine Log360
Log360's September build fixes the migration to the unified console.
A side-by-side editorial comparison of Apache Storm and Tautulli — release velocity, themes, recent moves, and the top alternatives to consider.
Storm 3.1 adds an Iceberg sink and closes a long list of security gaps in Nimbus and the UI.
Storm runs a 3.x line, started in July with 3.0.0's removal of all Clojure and a Java 21 baseline, alongside 2.8.x maintenance. 3.1.0 on September 12 adds a storm-iceberg module with an Apache Iceberg sink bolt and a setting to control JSONP wrapping, and spends most of its notes on hardening: log listings filtered by user permission, jar locations restricted to the Nimbus inbox, blobstore names confined to topology directories, TLS peer verification for worker connections and required Kryo class registration.
Tautulli 2.18.2 fixes history grouping and closes another newsletter path traversal.
Tautulli, the Plex monitoring tool, shipped v2.18.2 in late September: history grouping now requires a matching guid, paused notifications stop repeating during buffering, and another path traversal in newsletter filenames is closed. It also adds Windows installer flags and loudness data in exports. The 2.18.0 feature release before it added Dolby Atmos and a push relay to replace OneSignal.
Storm runs a 3.x line, started in July with 3.0.0's removal of all Clojure and a Java 21 baseline, alongside 2.8.x maintenance. 3.1.0 on September 12 adds a storm-iceberg module with an Apache Iceberg sink bolt and a setting to control JSONP wrapping, and spends most of its notes on hardening: log listings filtered by user permission, jar locations restricted to the Nimbus inbox, blobstore names confined to topology directories, TLS peer verification for worker connections and required Kryo class registration.
After the 2.8.6 and 2.8.7 CVE releases, the 3.x line is closing access-control gaps across Nimbus, the logviewer and worker transport. The Iceberg sink adds a direct path into lakehouse storage.
Expect 3.1.x follow-ups, possibly with security advisories for the hardened paths, and continued 2.8.x maintenance; whether more lakehouse connectors follow is unclear.
Tautulli, the Plex monitoring tool, shipped v2.18.2 in late September: history grouping now requires a matching guid, paused notifications stop repeating during buffering, and another path traversal in newsletter filenames is closed. It also adds Windows installer flags and loudness data in exports. The 2.18.0 feature release before it added Dolby Atmos and a push relay to replace OneSignal.
Releases keep pairing a steady flow of security reports with small community-contributed features. History correctness is the other recurring thread, with regrouping logic changed so existing history splits by guid.
Expect another 2.18.x patch of the same shape, with at least one security fix, since every release in the past year has carried one.
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 Apache Storm or Tautulli.
Log360's September build fixes the migration to the unified console.
Deepnote's agent now runs from first prompt to finished notebook without handoffs.
HertzBeat's 1.9.0 is on its second release candidate, and the feed still skips 1.8.0.
OpenPanel moves from 3.18 to 3.20 in two days, still without a word of release notes.
TsFile 2.5 adds Go to its Java, C++ and Python implementations.
After a year of CVE fixes, Glances 4.5.7 turns to making its alerts tell the truth.
See all Apache Storm alternatives → · See all Tautulli alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache Storm and Tautulli are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Apache Storm and Tautulli are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Apache Storm alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Storm alternatives" section above for the current picks, or visit /alternatives/storm for the full list with editorial commentary on each.
Top Tautulli alternatives in Analytics are ranked by recent ship velocity. Browse the "Tautulli alternatives" section above for the current picks, or visit /alternatives/tautulli for the full list with editorial commentary on each.