mirror of
https://github.com/grafana/grafana.git
synced 2024-12-30 10:47:30 -06:00
Docs: replace broken link with current docs location (#74884)
Replaced broken link with current docs location
This commit is contained in:
parent
2c6958a14a
commit
fb91919e3b
@ -90,7 +90,7 @@ The new heatmap by default assumes that the data is pre-bucketed. So if your que
|
||||
|
||||
Grafana Alerting is now on by default if you upgrade from an earlier version of Grafana. If you have been using legacy alerting in an earlier version of Grafana and you upgrade to Grafana 9 your alert rules will be automatically migrated and the legacy alerting interface will be replaced by the Grafana Alerting interface.
|
||||
|
||||
Grafana Alerting, called unified alerting in Grafana 8, has been available since June, 2021 now provides feature parity with legacy alerting and many additional benefits. To find out more on the process to revert back to legacy alerts if needed, click [here]({{< relref "../alerting/migrating-alerts/opt-out" >}}). Note that if you do revert back (by setting the Grafana config flag GF_UNIFIED_ALERTING_ENABLED to false), that we expect to remove legacy alerting in the next major Grafana release, Grafana 10.
|
||||
Grafana Alerting, called unified alerting in Grafana 8, has been available since June, 2021 now provides feature parity with legacy alerting and many additional benefits. To find out more on the process to revert back to legacy alerts if needed, click [here]({{< relref "../alerting/set-up/migrating-alerts#opt-out" >}}). Note that if you do revert back (by setting the Grafana config flag GF_UNIFIED_ALERTING_ENABLED to false), that we expect to remove legacy alerting in the next major Grafana release, Grafana 10.
|
||||
|
||||
### Alert state history for Grafana managed alerts
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user