e2e-alertmanager-test

name	e2e-alertmanager-test
description	Render end-to-end previews of what an alert notification will actually look like (plain-text email, HTML email, Slack attachment JSON, raw webhook JSON) by replaying a Prometheus unit-test file's expected alerts through a live Alertmanager. Effectively a "print preview" for alerts. Use to review notification formatting/content before merging alert changes, or in CI against an ephemeral Alertmanager to produce a diffable preview artifact. Requires a reachable Alertmanager API and a promtool-style unit-test file as input. Can be made fully hermetic in CI by pointing the ephemeral Alertmanager at a skeleton config that keeps the team's real routing/grouping/inhibition rules but overrides receiver connection details, so no real notification ever leaves the runner.
license	BSD-3-Clause

e2e-alertmanager-test

Takes the exp_alerts fixtures out of a Prometheus promtool-style unit test file, POSTs each one to a real Alertmanager's /api/v2/alerts endpoint, and renders what the resulting notification would look like in several formats. It does not test routing/inhibition logic inside this tool itself — it exercises whatever routing your target Alertmanager instance is actually configured with, and shows you the rendered output.

When to use this skill

• Before merging an alert change, to see the actual notification content (subject line, body, Slack attachment) a human on-call would receive — not just "does it fire," but "does it read well."
• As a CI step against a throwaway/ephemeral Alertmanager container, producing a rendered-output artifact that reviewers can diff between runs, the same way a UI snapshot test is diffed. Fed a skeleton config (see below), this run is fully hermetic — see Achieving full hermeticity in CI.