Glances
Glances 4.5.9 closes out the 4.x line as a 5.0 beta opens for testing.
A side-by-side editorial comparison of Marquez and Apache SkyWalking — release velocity, themes, recent moves, and the top alternatives to consider.
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
SkyWalking 11.1 builds service maps from OpenTelemetry traces, no SkyWalking agent required.
Apache SkyWalking spent 2025 and 2026 rebuilding its foundations: BanyanDB replaced H2, the Groovy DSL runtime gave way to ANTLR4 and Javassist, and 11.0.0 split the UI out of the backend. Version 11.1.0, released November 6, stores OTLP traces as they arrive and adds a Trace Analysis Language that turns spans into service, instance and endpoint metrics, topology and dashboards for the databases, caches and queues those services call. Applications instrumented only with OpenTelemetry SDKs now get SkyWalking's dashboards without its agent.
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
The arc is a backend project growing a front end: lineage data that existed in the API was progressively given pages, panels and paging, and by 0.50.0 the framing had shifted from lineage graph to observability dashboard. Tagging deepened in the same period, moving from dataset tags to field-level tags to job tags. That arc stops abruptly — 0.50.0 in October 2024 is the last entry, with nothing published in the roughly two years since.
The entries give no roadmap signal past 0.50.0, and the job-to-job lineage change was explicitly framed as a prompt for a wider parent/child hierarchy discussion that no later release picks up, so that hierarchy work is best read as unfinished rather than planned.
Apache SkyWalking spent 2025 and 2026 rebuilding its foundations: BanyanDB replaced H2, the Groovy DSL runtime gave way to ANTLR4 and Javassist, and 11.0.0 split the UI out of the backend. Version 11.1.0, released November 6, stores OTLP traces as they arrive and adds a Trace Analysis Language that turns spans into service, instance and endpoint metrics, topology and dashboards for the databases, caches and queues those services call. Applications instrumented only with OpenTelemetry SDKs now get SkyWalking's dashboards without its agent.
After taking storage and runtime in-house, SkyWalking is opening its front door to OpenTelemetry data. Its value is shifting from its own agents toward the analysis it runs on any trace source.
Expect more TAL coverage and OpenTelemetry quick starts, with SkyWalking's own agents positioned as optional rather than required.
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 Marquez or Apache SkyWalking.
Glances 4.5.9 closes out the 4.x line as a 5.0 beta opens for testing.
Calibre MCP lets your coding agent read RUM and Lighthouse data, then fix the slow code
Dovetail opens its docs to Claude and ChatGPT as co-authors.
OpenReplay's feed is Helm chart bumps behind its asset-cacher deny list.
Tinybird shrinks its Local image by a third after a run of observability updates.
OpenHouse tightens view authorization and moves its optimizer schema to Flyway.
See all Marquez alternatives → · See all Apache SkyWalking alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — observability — within Analytics. Apache SkyWalking is currently shipping more aggressively (velocity 3.8 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. Apache SkyWalking is currently shipping more aggressively (velocity 3.8 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 Marquez alternatives in Analytics are ranked by recent ship velocity. Browse the "Marquez alternatives" section above for the current picks, or visit /alternatives/marquez for the full list with editorial commentary on each.
Top Apache SkyWalking alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache SkyWalking alternatives" section above for the current picks, or visit /alternatives/skywalking for the full list with editorial commentary on each.