prometheus / prometheus/alertmanager
Alert grouping test with amtool
Open
@SoloJacobs is already working on this.
Since Feb 25, 2026.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
What did you do?
Now we are activly using amtool config routes test and find it extremely usefull, but recently found that we should check if alert grouping is expected too.
for example
now we are checking that
% amtool config routes test --config.file alertmanager.yaml --tree \
--verify.receivers wire-team-opsgenie 'team=wire'
Matching routes:
.
└── default-route
└── {team=~"^(?:^(wire)$)$"} receiver: wire-team-opsgenie
wire-team-opsgenie
it will be usefull if we can pass something like
% amtool config routes test --config.file alertmanager.yaml \
--tree --verify.receivers wire-team-opsgenie \
--verify.grouping=env,cluster,priority 'team=wire'
Matching routes:
.
└── default-route
└── {team=~"^(?:^(wire)$)$"} receiver: wire-team-opsgenie
wire-team-opsgenie, grouping: [env,cluster,priority]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.