Deduplicating Alerts
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, prometheus
- Domain
- cloud, observability
Research direction
Start by reviewing Azure Monitor Prometheus alert evaluation and notification behavior for the described rule group and Slack webhook setup. Determine whether alert deduplication or updating existing alerts is supported, and document the relevant configuration or confirm that the capability is not implemented.
Written by the indexing model from the issue text.
Description
Hi team, currently I have this setup:
- Prometheus rule group with scope of Azure Monitor Workspace
- The rules in the rule group have an action group associated, which will call a HTTP based slack webhook to send alerts
What I'm trying to achieve:
- When the condition is met for a certain rule, I expected the alert to fire once and subsequent evaluations to the rule to either do nothing or update to the existing alert
Current reality of my setup:
- When the condition is met for a certain rule, new alerts will keep firing on each subsequent evluation of the rule
I've tried looking for configuration that will help me achieve the desired behavior but with no luck.
So far I've tried:
- Setting the evaluation interval to a higher value, but this only delays the alert firing, not deduplicate it
- Processing rule to supress alerts, but it seems to only supress by time of day etc, not deduplicate
Is there a config that I'm not aware of or is this a mechanism not yet implemented in Azure Monitor?
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from microsoft/AzureMonitorCommunity
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
All issues in microsoft/AzureMonitorCommunity
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carverauto/serviceradar#4596 ·
-
complexity: small feature: security role: DevOps Engineer size: 2pt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
hackforla/devops-security#203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenHands/OpenHands-Cloud#1283 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elecnix/infra-cost-model#353 ·