Docs: update Legacy alerting deprecation to pass doc-validator (#69192)

* baldm0mma/doc-val/ update paths

* baldm0mma/doc-val/ update path

* baldm0mma/doc-val/ update trailing comma

* baldm0mma/doc-val
This commit is contained in:
Jev Forsberg 2023-05-26 13:46:14 -06:00 committed by GitHub
parent fa6afc7ea4
commit 731efdf7f4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -29,11 +29,11 @@ The new system is based on Prometheus Alertmanager, which offers a more comprehe
Overall, the new alerting system in Grafana is a major improvement over the legacy alerting feature, providing users with a more powerful and flexible alerting experience.
Additionally, legacy alerting still requires Angular to function and we are [planning to remove support for it]({{< relref ".../developers/angular_deprecation" >}}) in Grafana 11.
Additionally, legacy alerting still requires Angular to function and we are [planning to remove support for it]({{< relref "../../developers/angular_deprecation" >}}) in Grafana 11.
## When will we remove legacy alerting completely?
Legacy alerting will be removed from the code-base in Grafana 11, following the same timeline as the [Angular deprecation]({{< relref ".../developers/angular_deprecation" >}}).
Legacy alerting will be removed from the code-base in Grafana 11, following the same timeline as the [Angular deprecation]({{< relref "../../developers/angular_deprecation" >}}).
## How do I migrate to the new Grafana alerting?
@ -43,4 +43,4 @@ Refer to our [migration instructions]({{< relref "./opt-in" >}}).
- [Upgrade Alerting]({{< relref "./_index.md" >}})
- [Legacy alerting differences and limitations]({{< relref "./_index.md" >}})
- [Angular support deprecation]({{< relref ".../developers/angular_deprecation/" >}})
- [Angular support deprecation]({{< relref "../../developers/angular_deprecation" >}})