← Back to home
Comparison · Infra & APIs

Prometheus Alertmanager vs Skipper

A side-by-side editorial comparison of Prometheus Alertmanager and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.

Prometheus Alertmanager vs Skipper: at a glance

FeaturePrometheus AlertmanagerSkipper
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesalerting, prometheus, refactor, dispatcherreverse-proxy, http-routing, dependency-hygiene, release-per-commit
Last editorial update3h ago11h ago
WebsiteVisit →Visit →

What is Prometheus Alertmanager?

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.

Read the full Prometheus Alertmanager trajectory →

What is Skipper?

Skipper tags a release per commit — nine in eight days, and none of them change routing.

Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.

Read the full Skipper trajectory →

Prometheus Alertmanager vs Skipper: editorial side-by-side

P0.0

Alertmanager is dismantling its global state one contention bug at a time

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

S
Skipper
INFRA · APIS
5.0

Skipper tags a release per commit — nine in eight days, and none of them change routing.

◆ Current state

Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.

◆ Where it's heading

Nothing in these entries points to a direction change; the 0.27 line is in steady maintenance with supply-chain hygiene as the visible priority — oras-go pinned to a released version so osv-scanner stops flagging it, the CodeQL action upgraded, an OPA test hardened to deny requests with truncated bodies. The documentation change is the most revealing item: jwtValidation's behavior was unclear enough to prompt a proposed advisory, and the response was to clarify the docs rather than alter the code.

◆ Prediction

The tag stream will most likely continue at several releases a week with the same composition of dependency bumps and test fixes. These entries show no feature work in flight, so the next notable change is more likely another security-adjacent clarification than a new routing capability.

Alternatives to Prometheus Alertmanager and Skipper

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 Skipper.

See all Prometheus Alertmanager alternatives → · See all Skipper alternatives →

Recent activity from Prometheus Alertmanager and Skipper

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 16h agoSkipperPin oras-go to a released version to satisfy osv-scanner
  2. 1d agoSkipperClarify jwtValidation behavior after a proposed advisory
  3. 1d agoSkipperRefactor Valkey Del and ratelimit ring client injection
  4. 1d agoSkipperBump the CodeQL upload-sarif action to 4.37.6
  5. 1d agoSkipperBump 14 Go modules, including OpenTelemetry and go-redis
  6. 4d agoSkipperFix the proxy listener binding on an insecure address
  7. 1mo agoPrometheus AlertmanagerSilence snapshot compatibility fix in Alertmanager 0.33.1
  8. 1mo agoPrometheus AlertmanagerPer-group alert markers replace the global marker in 0.33.0
  9. 2mo agoPrometheus AlertmanagerDispatcher goroutine leak fix in Alertmanager 0.32.2
  10. 3mo agoPrometheus AlertmanagerContended-route dispatch fix in Alertmanager 0.32.1
  11. 3mo agoPrometheus Alertmanager0.32.1-rc.0 / 2026-04-27
  12. 4mo agoPrometheus AlertmanagerAlertmanager 0.32.0 stops shipping compiled UI assets in-tree

Frequently asked questions

What is the difference between Prometheus Alertmanager and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.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.

Is Prometheus Alertmanager better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Prometheus Alertmanager?

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.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.