* remove unused compat functions
* update to alerting module from pr
* replace IntegrationConfig with IntegrationSchemaVersion
* safely resolve a string into integration type
* change usages of integration config
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (1) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (2) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (3) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (4) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (5) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (6) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (7) (push) Waiting to runDetails
Frontend tests / Unit tests (${{ matrix.chunk }} / 8) (8) (push) Waiting to runDetails
Integration Tests / Sqlite (push) Waiting to runDetails
Integration Tests / MySQL (push) Waiting to runDetails
Integration Tests / Postgres (push) Waiting to runDetails
Run dashboard schema v2 e2e / dashboard-schema-v2-e2e (push) Waiting to runDetails
Dispatch sync to mirror / dispatch-job (push) Waiting to runDetails
Trivy Scan / trivy-scan (push) Waiting to runDetails
publish-kinds-next / config (push) Has been cancelledDetails
publish-kinds-next / main (push) Has been cancelledDetails
* add active_time_intervals to route model
* update k8s compat layer
* update notification policies service to validate active time intervals
* update integration tests
* update openapi
* add active time interval to model
* update route generator to include active time interval
* Update storage list and rename methods to handle active intervals
* update api model
* update provisioning and export models
* update ui to allow active timing config
* update i18n
* fix snapshots for ui tests
* run prettier
* Alerting: Active time intervals UI naming (#104402)
* update naming in UI
* update naming in the edit page title
* update translations
* update alerting module
---------
Signed-off-by: Yuri Tseretyan <yuriy.tseretyan@grafana.com>
Co-authored-by: Sonia Aguilar <33540275+soniaAguilarPeiron@users.noreply.github.com>
Co-authored-by: Sonia Aguilar <soniaaguilarpeiron@gmail.com>
What is this feature?
A follow-up for #101184, adds AlertRule.MissingSeriesEvalsToResolve to the APIs.
missing_series_evals_to_resolve must be specified too and it must be > 0.
POST /api/ruler/grafana/api/v1/rules/{folderUID} works in the following way:
If missing_series_evals_to_resolve is not sent or null, the rule keeps its existing value
If missing_series_evals_to_resolve > 0: updates to that value
If missing_series_evals_to_resolve = 0: resets to default (nil).
AlertRule.MissingSeriesEvalsToResolve can't be 0, so I used it to reset
In the Provisioning API, the value is just set if present and > 0. Otherwise it's reset:
PUT to /api/v1/provisioning/alert-rules/{UID}:
If missing_series_evals_to_resolve is nil, it's reset to the default value
If missing_series_evals_to_resolve > 0, it's updated
What is this feature?
This PR introduces a new alert rule configuration option, keep_firing_for (Prometheus documentation).
keep_firing_for prevents alerts from resolving immediately after the alert condition returns to normal. Instead, they transition into a "Recovering" state and are not considered resolved by the Alertmanager. Once the recovery period ends (or after the next evaluation if it is bigger than keep_firing_for), the alert transitions to "Normal" if it doesn't start alerting again:
Before
+----------+ +----------+
| Alerting |---->| Normal |
+----------+ +----------+
-----
After
+----------+ +------------+ +----------+
| Alerting |----->| Recovering |---->| Normal |
+----------+ +------------+ +----------+
Why do we need this feature?
This feature prevents flapping alerts by adding a recovery period. This helps avoid false resolutions caused by brief alert
Yuri Tseretyan
Tito Lins
Alexander Akhmetov
Steve Simpson