3
0
mirror of https://github.com/grafana/grafana.git synced 2025-02-25 18:55:37 -06:00
grafana/pkg/services/ngalert/eval
gotjosh c631261681
Alerting: Attempt to retry retryable errors ()
* Alerting: Attempt to retry retryable errors

Retrying has been broken for a good while now (at least since version 9.4) - this change attempts to re-introduce them in their simplest and safest form possible.

I first introduced  to make sure we don't disrupt or put additional load on our customer's data sources with this change in a patch release. Paired with this change, retries can now work as expected.

There's two small differences between how retries work now and how they used to work in legacy alerting.

Retries only occur for valid alert definitions - if we suspect that that error comes from a malformed alert definition we skip retrying.
We have added a constant backoff of 1s in between retries.

---------

Signed-off-by: gotjosh <josue.abreu@gmail.com>
2023-12-06 20:45:08 +00:00
..
eval_mocks Chore: use any rather than interface{} () 2023-08-30 18:46:47 +03:00
context.go NGAlerting: Use identity.Requester interface instead of SignedInUser () 2023-11-14 14:47:34 +00:00
eval_bench_test.go Alerting: Improve performance of matching captures () 2023-07-20 09:07:00 +01:00
eval_test.go Alerting: Attempt to retry retryable errors () 2023-12-06 20:45:08 +00:00
eval.go Alerting: Attempt to retry retryable errors () 2023-12-06 20:45:08 +00:00
extract_md_test.go Chore: use any rather than interface{} () 2023-08-30 18:46:47 +03:00
extract_md.go Alerting: Sort NumberCaptureValues in EvaluationString () 2023-07-19 12:09:21 +01:00
testing.go Alerting: Refactor of state manager tests () 2023-08-04 13:39:49 -04:00