# amtool config routes test assertions.
# Alertmanager v0.34.1 does not evaluate active_time_intervals in
# `amtool config routes test`. warning+platform therefore resolves to
# slack-platform even outside business-hours. See policies/pint-exceptions.md.
cases:
- name: critical_platform_instance_down
labels:
alertname: InstanceDown
severity: critical
team: platform
service: node
instance: node-a.larkspur.example:9100
receivers: [pagerduty-oncall, slack-incidents]
- name: critical_orders_fast_burn
labels:
alertname: OrdersApiErrorBudgetBurnFast
severity: critical
team: orders
service: orders-api
receivers: [pagerduty-oncall, slack-incidents, email-oncall]
- name: critical_payments
labels:
alertname: PaymentsDown
severity: critical
team: payments
service: payments-worker
receivers: [pagerduty-oncall, slack-incidents, slack-payments]
- name: warning_orders_slow_burn
labels:
alertname: OrdersApiErrorBudgetBurnSlow
severity: warning
team: orders
service: orders-api
receivers: [email-oncall]
- name: warning_payments_queue
labels:
alertname: PaymentsQueueBacklog
severity: warning
team: payments
service: payments-worker
receivers: [slack-payments]
- name: warning_platform_memory
labels:
alertname: NodeMemoryHigh
severity: warning
team: platform
service: node
instance: node-a.larkspur.example:9100
receivers: [slack-platform]
note: amtool ignores active_time_intervals and mute_time_intervals
- name: info_discarded
labels:
alertname: Notice
severity: info
team: platform
receivers: ["null"]
- name: watchdog_deadman
labels:
alertname: Watchdog
severity: info
team: platform
receivers: [deadman-webhook]
- name: unclassified_default
labels:
alertname: Unclassified
receivers: [default]