DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
A side-by-side editorial comparison of Prometheus Alertmanager and Fission — release velocity, themes, recent moves, and the top alternatives to consider.
Alertmanager is dismantling its global state one contention bug at a time
Prometheus Alertmanager is in a maintenance-plus-refactor phase. The 0.32 and 0.33 lines are dominated by internal restructuring — the global alert marker replaced by per-aggregation-group markers, types moved out of shared packages, function signatures changed across the codebase — alongside a steady run of dispatcher fixes for contended routes and goroutine leaks. User-facing additions are modest but real: silence annotations in the UI, receiver labels and filtering on the v2 API, and a structured event recorder behind a feature flag.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Prometheus Alertmanager is in a maintenance-plus-refactor phase. The 0.32 and 0.33 lines are dominated by internal restructuring — the global alert marker replaced by per-aggregation-group markers, types moved out of shared packages, function signatures changed across the codebase — alongside a steady run of dispatcher fixes for contended routes and goroutine leaks. User-facing additions are modest but real: silence annotations in the UI, receiver labels and filtering on the v2 API, and a structured event recorder behind a feature flag.
Two threads run in parallel. The first is unwinding shared mutable state: the global marker removal and the per-group marker introduction are the same fix applied structurally rather than patched, and the dispatcher bugfixes in 0.32.1 and 0.32.2 read as the symptoms that motivated it. The second is tightening the build and integration boundary — compiled UI assets left the repository in 0.32.0, and internal signatures changed with an explicit warning to downstream integrators. Neither is a feature push; both make the project easier to change later.
The event recorder is gated behind --enable-feature=event-recorder, which is the same staging pattern the project used for flags it later promoted or dropped; expect its status to be resolved in the next minor. Whether more of the marker refactor remains is not visible from these notes.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
Other Infra & APIs 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 Prometheus Alertmanager or Fission.
DNSControl is rewriting its record internals in public, one release candidate at a time
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeePass-compatible password manager frozen mid-patch-run since 2021.
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all Prometheus Alertmanager alternatives → · See all Fission alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Prometheus Alertmanager and Fission 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. Prometheus Alertmanager and Fission 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 Infra & APIs products to evaluate alongside.
Top Prometheus Alertmanager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Prometheus Alertmanager alternatives" section above for the current picks, or visit /alternatives/alertmanager for the full list with editorial commentary on each.
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.