IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-25 18:55:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

Docs: changes to upgrade docs (#69127)

Browse Source 
* Docs: changes to upgrade docs

* updates links

* fixes links

* fixes links

* fixes deprecation message
This commit is contained in:
brendamuir 2023-05-26 17:49:11 +02:00 committed by GitHub
parent 6b67bade55
commit 6bd3d4bf61
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/sources/alerting/migrating-alerts/_index.md
View File

@ -36,4 +36,4 @@ The following table provides details on the upgrade for Cloud, Enterprise, and O
| Enterprise | Existing Enterprise instances using legacy alerting will have both the old (marked as legacy) and the new alerting icons in the navigation panel. During upgrade, existing legacy alerts are migrated to Grafana Alerting. If you wish, you can [opt-out]({{< relref "./opt-out" >}}) of Grafana Alerting and roll back to legacy alerting. In that case, you can manage your legacy alerts from the alerting icon marked as legacy. | | Enterprise | Existing Enterprise instances using legacy alerting will have both the old (marked as legacy) and the new alerting icons in the navigation panel. During upgrade, existing legacy alerts are migrated to Grafana Alerting. If you wish, you can [opt-out]({{< relref "./opt-out" >}}) of Grafana Alerting and roll back to legacy alerting. In that case, you can manage your legacy alerts from the alerting icon marked as legacy. |
| OSS | Existing OSS installations with legacy dashboard alerting will have two alerting icons in the left navigation panel - the old alerting icon (marked as legacy) and the new Grafana Alerting icon. During upgrade, existing legacy alerts are migrated to Grafana Alerting. If you wish, you can [opt-out]({{< relref "./opt-out" >}}) of Grafana Alerting and roll back to legacy alerting. In that case, you can manage your legacy alerts from the alerting icon marked as legacy. | | OSS | Existing OSS installations with legacy dashboard alerting will have two alerting icons in the left navigation panel - the old alerting icon (marked as legacy) and the new Grafana Alerting icon. During upgrade, existing legacy alerts are migrated to Grafana Alerting. If you wish, you can [opt-out]({{< relref "./opt-out" >}}) of Grafana Alerting and roll back to legacy alerting. In that case, you can manage your legacy alerts from the alerting icon marked as legacy. |
> **Note:** Legacy alerting will be deprecated in a future release (v10). > **Note:** Starting with v9.0, legacy alerting is deprecated and will be removed in a future release.

18
docs/sources/alerting/legacy-alerting-deprecation.md → docs/sources/alerting/migrating-alerts/legacy-alerting-deprecation.md
View File

@ -1,7 +1,7 @@
--- ---
title: Legacy alerting deprecation title: Legacy alerting deprecation
description: Legacy alerting deprecation notice description: Legacy alerting deprecation notice
weight: 999 weight: 107
keywords: keywords:
- grafana - grafana
- alerting - alerting
@ -19,7 +19,7 @@ Users who are still using legacy alerting are encouraged to migrate their alerts
However, we will still patch CVEs until legacy alerting is completely removed in Grafana 11; honoring our commitment to building and distributing secure software. However, we will still patch CVEs until legacy alerting is completely removed in Grafana 11; honoring our commitment to building and distributing secure software.
We have provided [instructions]({{< relref "./migrating-alerts" >}}) on how to migrate to the new alerting system, making the process as easy as possible for users. We have provided [instructions]({{< relref "./_index.md" >}}) on how to migrate to the new alerting system, making the process as easy as possible for users.
## Why are we deprecating legacy alerting? ## Why are we deprecating legacy alerting?
@ -29,18 +29,18 @@ 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. 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? ## 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? ## How do I migrate to the new Grafana alerting?
Refer to our [migration instructions]({{< relref "./migrating-alerts/opt-in" >}}). Refer to our [migration instructions]({{< relref "./opt-in" >}}).
### Links ### Useful links
- [Upgrade Alerting]({{< relref "./migrating-alerts" >}}) - [Upgrade Alerting]({{< relref "./_index.md" >}})
- [Legacy alerting differences and limitations]({{< relref "./migrating-alerts/migrating-legacy-alerts" >}}) - [Legacy alerting differences and limitations]({{< relref "./_index.md" >}})
- [Angular support deprecation]({{< relref "../developers/angular_deprecation" >}}) - [Angular support deprecation]({{< relref ".../developers/angular_deprecation/" >}})