grafana

The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.

prometheus hacktoberfest metrics monitoring alerting grafana go influxdb mysql postgres analytics data-visualization dashboard business-intelligence elasticsearch

History

Matthew Jacobson 0424d44b39 Alerting: In migration, create one label per channel (#76527 ) * 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.		1 year ago
..
models	Alerting: In migration, create one label per channel (#76527 )	1 year ago
store	Alerting: In migration, create one label per channel (#76527 )	1 year ago
alert_rule.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
alert_rule_test.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
channel.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
channel_test.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
cond_trans.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
cond_trans_test.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
migration_test.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
models.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
permissions.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
permissions_test.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
securejsondata.go	Alerting: Move legacy alert migration from sqlstore migration to service (#72702 )	2 years ago
service.go	Alerting: Add clean_upgrade config and deprecate force_migration (#78324 )	2 years ago
service_test.go	Alerting: Add clean_upgrade config and deprecate force_migration (#78324 )	2 years ago
silences.go	Alerting: Handle custom dashboard permissions in migration service (#74504 )	2 years ago
template.go	Alerting: Handle edge cases without panicking during template migration (#76890 )	2 years ago
template_test.go	Alerting: Handle edge cases without panicking during template migration (#76890 )	2 years ago
testing.go	Alerting: Fix flaky SQLITE_BUSY when migrating with provisioned dashboards (#76658 )	2 years ago
ualert.go	Alerting: In migration, create one label per channel (#76527 )	1 year ago
ualert_test.go	Alerting: In migration improve deduplication of title and group (#78351 )	2 years ago