Workflow: Integration Testing
Step-by-step guide for verifying the full notification pipeline — from Alertmanager routing to actual message delivery in Slack, PagerDuty, email, or webhooks.
When to Use
Use this workflow when:
- Setting up a new receiver (Slack channel, PagerDuty service, email group)
- Verifying that routing rules deliver alerts to the right integration
- Debugging notification delivery issues
Journey
Step-by-Step
| Step | Action | Tool / Resource | Key Parameters |
|---|---|---|---|
| 1 | Check receivers | Resource: am://system/receivers | Verify target receiver is configured |
| 2 | Simulate routing | am_explain_routing(labels={"alertname": "MCPIntegrationTest", "team": "sre", "severity": "warning"}) | Confirm routing to target |
| 3 | Push test alert | am_push_test_alert(alert_labels={"alertname": "MCPIntegrationTest", "team": "sre", "severity": "warning"}) | Fires a real alert |
| 4 | Verify receipt | (Manual) — user confirms alert arrived in Slack/PagerDuty/email | — |
| 5 | Debug if needed | Resource: am://system/config | Check routing tree |
Guided Prompt: Use
am-integration-test-guidedfor the full step-by-step flow.
Important
am_push_test_alert fires a real alert into Alertmanager. Downstream integrations will receive actual notifications. Use descriptive labels like alertname: "MCPIntegrationTest" to distinguish test alerts.
Next Steps
- Governance — Compliance review and audit
- Alert Triage — On-call triage workflow
- Maintenance Silence — Safe silence lifecycle