You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the recommended notation for ungrouping (i.e. group_by: ['...']) , I have the following configuration to ungroup alerts but it is not working as expected:
I can manually trigger several alerts on the associated Alert rule, within a 5m interval, but when I check the AlertManager UI I see only 1 alert instance.
A quick check of the Alert rule's PromQL returns the correct value as per the manual triggers I have done, but the number of alerts in AlertManager UI still does not match.
My expectation is that when I trigger, say 5 alerts within a 5m interval, the AlertManager UI should show , at most 5 separate alerts. For now I am only getting a single alert.
The Alert rule:
alert = "repo.rename"
expr = "sum(count_over_time({stream=\"github_audit_log\"} | json | action = `repo.rename`[5m])) > 0"
labels = {
severity = "critical"
source = "github"
type = "pagerduty"
service = "gitops"
}
annotations = {
managed_by = "mycorp/iac"
summary = "A repository was renamed."
}
}```
What am I missing ? Does the `group_by: ['...']` notation actually work?
The text was updated successfully, but these errors were encountered:
Using the recommended notation for ungrouping (i.e.
group_by: ['...']
) , I have the following configuration to ungroup alerts but it is not working as expected:I can manually trigger several alerts on the associated Alert rule, within a 5m interval, but when I check the AlertManager UI I see only 1 alert instance.
A quick check of the Alert rule's PromQL returns the correct value as per the manual triggers I have done, but the number of alerts in AlertManager UI still does not match.
My expectation is that when I trigger, say 5 alerts within a 5m interval, the AlertManager UI should show , at most 5 separate alerts. For now I am only getting a single alert.
The Alert rule:
The text was updated successfully, but these errors were encountered: