Omni
Omni adds embed MCP tokens and webhook delivery for AI routines.
A side-by-side editorial comparison of GoAccess and Apache Storm — release velocity, themes, recent moves, and the top alternatives to consider.
GoAccess 1.12 splits AI crawlers from search bots in web log reports.
GoAccess is a mature open-source web log analyzer with a terminal UI and self-contained HTML reports. After 1.11's parsing and memory gains in July, 1.12 on September 16 adds a dedicated AI Crawlers category separating AI assistants and training bots from search crawlers, a Fediverse category, a live requests-per-second rate and an option to exclude traffic by ASN. It also refuses database restores whose grouping settings no longer match.
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.
GoAccess is a mature open-source web log analyzer with a terminal UI and self-contained HTML reports. After 1.11's parsing and memory gains in July, 1.12 on September 16 adds a dedicated AI Crawlers category separating AI assistants and training bots from search crawlers, a Fediverse category, a live requests-per-second rate and an option to exclude traffic by ASN. It also refuses database restores whose grouping settings no longer match.
GoAccess is adapting its traffic classification to how sites are now crawled, with AI bots and Fediverse servers as distinct sources. Releases continue on a roughly two-to-five-month cycle.
Expect more bot classification and filtering options in the next release; timing is unclear.
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.
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 GoAccess or Apache Storm.
Omni adds embed MCP tokens and webhook delivery for AI routines.
This feed samples OpenSearch Dashboards; its latest entry is a 2.19.7 notes commit.
Iceberg 1.12 drops Spark 3.4 and starts laying groundwork for the v4 table spec.
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.
See all GoAccess alternatives → · See all Apache Storm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GoAccess and Apache Storm 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. GoAccess and Apache Storm 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 GoAccess alternatives in Analytics are ranked by recent ship velocity. Browse the "GoAccess alternatives" section above for the current picks, or visit /alternatives/goaccess for the full list with editorial commentary on each.
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.