Disable Alerts after 7 days?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud, observability
Research direction
Start with the issue's questions about Azure Monitor alert rules, the seven-day failure disablement, and differences between v1 and v2 rules. Check the relevant Azure Monitor documentation and record whether the behavior applies, how missing tables or columns are treated, and whether it can be prevented; done means each question has a clear documented answer.
Written by the indexing model from the issue text.
Description
I have a question related to behaviour as seen below.
We deploy about 300 alerts for our customers which are mostly based upon log searches.
I gave read that when an alert rule is failing for 7 days it gets disabled automatically.
As I understood the documentation this also happens when the syntax of the query is ok but if the table/column does not yet exist in log analytics.
Since we bootstrap our environments with all these alerts it could obviously be that a customer will not deploy all the resources that have an alert within a 7 day period. It could take months for somebody to actually deploy an AKS cluster for example.
Is the "7 day disable automation by MS" applicable to:
- v1 and v2 alert rules
Is there a way to prevent this from happening?
Did I understand the mechanism correctly?
"alert 123 is disabled by the System due to : Alert has been failing consistently with the same exception for the past week"
- 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
-
documentation improve or update documentation priority/low triage
Difficulty 2/5 Half a day Newbie friendliness 86/100
warpdotdev/docs#782 · 1 comment ·
-
EKS 1.35 Support Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gruntwork-io/kubergrunt#281 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ehmpathy/declastruct-aws#104 ·
-
enhancement service/sns
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hashicorp/terraform-provider-aws#50109 · 1 comment · 1 reaction ·
-
Product: Azure Policy :shield: Topic: Diagnostic Settings :test_tube: Topic: Policy :pencil:
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Azure/Azure-Landing-Zones#4283 · 1 comment ·