mirror of
https://github.com/grafana/grafana.git
synced 2025-02-25 18:55:37 -06:00
0424d44b39
* In migration, create one label per channel
This PR changes how routing is done by the legacy alerting migration.
Previously, we created a single label on each alert rule that contained an array of contact point names. Ex: __contact__="slack legacy testing","slack legacy testing2"
This label was then routed against a series of regex-matching policies with continue=true. Ex: __contacts__ =~ .*"slack legacy testing".*
In the case of many contact points, this array could quickly become difficult to manage and difficult to grok at-a-glance.
This PR replaces the single __contact__ label with multiple __legacy_c_{contactname}__ labels and simple equality-matching policies. These channel-specific policies are nested in a single route under the top-level route which matches against __legacy_use_channels__ = true for ease of organization.
This should improve the experience for users wanting to keep the default migrated routing strategy but who also want to modify which contact points an alert sends to.
|
||
|---|---|---|
| .. | ||
| admin_configuration_test.go | ||
| admin_configuration.go | ||
| alert_query_test.go | ||
| alert_query.go | ||
| alert_rule_test.go | ||
| alert_rule.go | ||
| alertmanager.go | ||
| constants.go | ||
| history.go | ||
| image_test.go | ||
| image.go | ||
| instance_labels.go | ||
| instance_test.go | ||
| instance.go | ||
| provisioning.go | ||
| testing.go | ||
| time.go | ||