alertmanager

Manage Alertmanager silences, routes, and status via its API.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill alertmanager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alertmanager
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/prometheus/alertmanager
Command: npx skills add https://github.com/theslashdojo/dojo --skill alertmanager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps operators and agents rapidly inspect and modify Alertmanager state so that alerts are routed correctly, noisy alerts are silenced during maintenance, and delivery issues are diagnosed during incidents.

Core Features & Use Cases

  • Status and diagnostics: Fetch cluster and config status and enumerate grouped alerts to understand delivery state.
  • Silence lifecycle management: Create narrowly scoped silences with matchers, expire silences safely, and list active silences for cleanup.
  • Routing validation: Validate and render routing trees using amtool or local config files before rollout to avoid misroutes.
  • Use Case: During a planned maintenance window, list matching alerts, create a short-lived silence scoped to specific instances, and validate routes to confirm notifications go to the intended receiver.

Quick Start

Use the alertmanager skill to list active silences and validate routing configuration against your alertmanager.yml.

Frequently Asked Questions about alertmanager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and manage Alertmanager silences during a maintenance window?

To manage Alertmanager silences during maintenance, you can create narrowly scoped silences using matchers, list active silences for cleanup, and safely expire them. This requires access to an Alertmanager API endpoint with optional bearer or basic auth.

How do I validate and render Alertmanager routing trees before a rollout?

You can validate and render Alertmanager routing trees using amtool or local config files. This process checks your alertmanager.yml configuration to prevent misroutes and confirm notifications reach the intended receiver before deployment.

What is the best way to inspect grouped alerts and diagnose delivery issues in Alertmanager?

Inspecting grouped alerts and diagnosing delivery issues involves fetching cluster and config status via the Alertmanager API. This enumerates current alert delivery states to help operators understand and resolve notification problems during incidents.

Can I use amtool to check Alertmanager routes against a local config file?

Yes, you can use amtool to validate and render routing trees against a local alertmanager.yml file. This allows you to verify routing configuration and matchers locally before applying changes to the live Alertmanager instance.

Do I need an Alertmanager API endpoint to list and expire active silences?

Yes, listing and expiring active silences requires access to an Alertmanager API endpoint. The endpoint supports optional bearer or basic auth, and accepts parameters like matchers, receivers, and RFC3339 timestamps to scope silences safely.

Why are my Prometheus alerts still firing after creating an Alertmanager silence?

Alertmanager silences must be narrowly scoped using correct matchers to suppress alerts. If the matcher parameters do not align with the firing alert labels, the alert will bypass the silence and continue routing to the configured receiver.