Dovetail
Channels stops labelling themes and starts tracking owned, priced-up ideas.
A side-by-side editorial comparison of dbt Core and ManageEngine Log360 — release velocity, themes, recent moves, and the top alternatives to consider.
Fusion's 2.0 train has become adapter work: Exasol from scratch, ClickHouse toward parity.
dbt-core is running two lines at once. The 2.0 Fusion train ships near-daily dev tags whose notes are dominated by adapter surface — an Exasol adapter built from nothing, ClickHouse being pulled up to what the Python adapter already does, and Databricks configuration filling in. The 1.x Python line, meanwhile, receives only backports: an Azure Blob artifact-upload fix and a sqlparse CVE pin, nothing else.
Log360 is collapsing a scattered suite into one console — and opening the migration door to it.
Two threads run through these builds. The first is consolidation: Unified Log360 is a centralized architecture pulling Log360 components and integrations into a single interface, and a PPM now lets standalone Log360 and EventLog Analyzer deployments carry supported configurations across. The second is a heavy security cadence — CVEs in this window include an unauthenticated local collector registration bypass, an authentication bypass allowing login as another user, and two authenticated RCE paths, alongside bundled PostgreSQL, Tomcat, Elasticsearch, and Kafka upgrades.
dbt-core is running two lines at once. The 2.0 Fusion train ships near-daily dev tags whose notes are dominated by adapter surface — an Exasol adapter built from nothing, ClickHouse being pulled up to what the Python adapter already does, and Databricks configuration filling in. The 1.x Python line, meanwhile, receives only backports: an Azure Blob artifact-upload fix and a sqlparse CVE pin, nothing else.
The recurring theme across dev.30, dev.33 and beta.2 is not new capability but acceptance: Fusion learning to take the config shapes dbt Core tolerates, ClickHouse incremental strategies resolving exactly like their Python counterparts, contracts and constraints enforced end-to-end. That is a rewrite closing the gap with the thing it replaces. The 1.x releases read as a maintenance line kept alive on security patches while attention sits on 2.0.
Expect the dev tags to keep grinding through adapter parity — ClickHouse projections and codec are named in the notes as available but not working yet, which is the next obvious box to tick. The 1.x branches will likely see only dependency and CVE releases.
Two threads run through these builds. The first is consolidation: Unified Log360 is a centralized architecture pulling Log360 components and integrations into a single interface, and a PPM now lets standalone Log360 and EventLog Analyzer deployments carry supported configurations across. The second is a heavy security cadence — CVEs in this window include an unauthenticated local collector registration bypass, an authentication bypass allowing login as another user, and two authenticated RCE paths, alongside bundled PostgreSQL, Tomcat, Elasticsearch, and Kafka upgrades.
ManageEngine is turning integrations into marketplace extensions rather than core releases — CrowdStrike Falcon Event Streams, Okta, Bitdefender GravityZone, and MikroTik all arrived that way, and extensions can now own a Dashboard tab. Combined with the Unified migration path and earlier work pulling NetFlow Analyzer, Firewall Analyzer, and the OpManager suite in as log sources, the shape is clear: one console, one log pipeline, and a plug-in surface where connector work happens. The recurring fixes around migration failures and service pack stacking suggest that transition is still bumpy in the field.
Expect connector coverage to keep expanding through the marketplace rather than through builds, and continued migration hardening as more standalone deployments move to Unified Log360. The steady CVE cadence points to further security patch builds on a two-to-four week rhythm.
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 dbt Core or ManageEngine Log360.
Channels stops labelling themes and starts tracking owned, priced-up ideas.
Chord is turning its analytics assistant into something with memory, and now feeding it more sources
Datawrapper ships one small fix at a time, each named for the chart it touches
After a summer fencing in its AI layer, Holistics points it at the question analysts get asked most.
Reporting tool turning itself into the place agencies prove AI visibility to clients
Stitch is running a fleet-wide Python 3.12 migration across its connector estate.
See all dbt Core alternatives → · See all ManageEngine Log360 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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. dbt Core is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
Top ManageEngine Log360 alternatives in Analytics are ranked by recent ship velocity. Browse the "ManageEngine Log360 alternatives" section above for the current picks, or visit /alternatives/manageengine-log360 for the full list with editorial commentary on each.