Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v10.1.x] Unified Alerting: Set max_attempts to 1 by default #79102

Merged
merged 1 commit into from Dec 5, 2023

Conversation

grafana-delivery-bot[bot]
Copy link
Contributor

Backport 0c9356a from #79095


The retry logic for unified alerting has been broken as far as v9.4.x, rather than fixing it in one go and causing a headache to our users with rules putting extra load on their datasources - I think a better approach is to simply set 1 as a default and then let our users change it.

I see two cons with this approach:

  • Configuration for legacy to unified alerting cannot be ported over automatically, users will have to manually set max_attempts to 3 when migrating.
  • Users expecting to get any sort of retrying (as with legacy alerting) will not have it out of the box and will have to manually edit the configuration.

I think this is the best compromise we can make with the introduction of #79037

Signed-off-by: gotjosh josue.abreu@gmail.com

* Unified Alerting: Set `max_attempts` to 1 by default

The retry logic for unified alerting has been broken as far as v9.4.x, rather than fixing it in one go and causing a headache to our users with rules putting extra load on their datasources - I think a better approach is to simply set 1 as a default and then let our users change it.

I see two cons with this approach:

- Configuration for legacy to unified alerting cannot be ported over automatically, users will have to manually set `max_attempts` to 3 when migrating.
- Users expecting to get any sort of retrying (as with legacy alerting) will not have it out of the box and will have to manually edit the configuration.

Signed-off-by: gotjosh <josue.abreu@gmail.com>
---------

Signed-off-by: gotjosh <josue.abreu@gmail.com>
(cherry picked from commit 0c9356a)
@grafana-delivery-bot grafana-delivery-bot bot added this to the 10.1.x milestone Dec 5, 2023
@grafana-delivery-bot grafana-delivery-bot bot requested review from papagian, zserge and yangkb09 and removed request for a team December 5, 2023 17:44
@grafana-delivery-bot grafana-delivery-bot bot added add to changelog area/backend backport A backport PR product-approved Pull requests that are approved by product/managers and are allowed to be backported type/docs labels Dec 5, 2023
@gotjosh gotjosh merged commit e102b64 into v10.1.x Dec 5, 2023
18 checks passed
@gotjosh gotjosh deleted the backport-79095-to-v10.1.x branch December 5, 2023 18:56
@aangelisc aangelisc modified the milestones: 10.1.x, 10.1.6 Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add to changelog area/backend backport A backport PR product-approved Pull requests that are approved by product/managers and are allowed to be backported type/docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants