I'm seeing issues with alert routing and trying to diagnose misconfiguration. Maybe someone will have an idea.
```
alertmanager --version
alertmanager, version 0.21.0 (branch: HEAD, revision: 4c6c03ebfe21009c546e4d1e9b92c371d67c021d)
build user: root@dee35927357f
build date: 20200617-08:54:02
go version: go1.14.4
```
```
route:
group_by:
- "..."
group_wait: 3s
group_interval: 10s
repeat_interval: 12h
receiver: alerts-webhook
routes:
- match:
severity: info
receiver: alerts-webhook
- match:
severity: critical
receiver: pagerduty
- match:
severity: warning
receiver: slack
receivers:
- name: alerts-webhook
webhook_configs:
send_resolved: true
slack_configs:
channel: "#info"
send_resolved: true
- name: pagerduty
pagerduty_configs:
- service_key: xxxyyyzzz
webhook_configs:
send_resolved: true
- name: slack
slack_configs:
send_resolved: true
webhook_configs:
send_resolved: true
```
In alertmanager logs I'm expecting all the notification severity info to be sent to alerts-webhook route:
```
sudo journalctl -u alertmanager | grep 'level=info' | tail -n 100 | awk '{ print $10 }'
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=slack
receiver=slack
receiver=slack
receiver=pagerduty
receiver=slack
receiver=slack
receiver=slack
receiver=slack
receiver=slack
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=pagerduty
receiver=alerts-webhook
receiver=pagerduty
```