IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-12-02 05:29:42 -06:00
Code Issues Packages Projects Releases Wiki Activity
3bd6b8a5ae
grafana/docs/sources/alerting/migrating-legacy-alerts.md
Jack Baldry 51dfcd7d37
Add current alias to all files (#48635) 
* Add aliases to all files

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>

* Prettify front matter

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
2022-05-17 08:24:11 -07:00

3.2 KiB
Raw Blame History

+++ aliases = ["/docs/grafana/latest/alerting/migrating-legacy-alerts/", "/docs/grafana/latest/alerting/unified-alerting/opt-in/"] description = "Migrate legacy dashboard alerts" title = "Migrating legacy dashboard alerts" weight = 114 +++

Migrating legacy dashboard alerts

When Grafana alerting is enabled or Grafana is upgraded to the latest version, existing legacy dashboard alerts migrate in a format compatible with the Grafana alerting. In the Alerting page of your Grafana instance, you can view the migrated alerts alongside new alerts.

Read and write access to legacy dashboard alerts and Grafana alerts are governed by the permissions of the folders storing them. During migration, legacy dashboard alert permissions are matched to the new rules permissions as follows:

  • If alert's dashboard has permissions, it will create a folder named like Migrated {"dashboardUid": "UID", "panelId": 1, "alertId": 1} to match permissions of the dashboard (including the inherited permissions from the folder).
  • If there are no dashboard permissions and the dashboard is under a folder, then the rule is linked to this folder and inherits its permissions.
  • If there are no dashboard permissions and the dashboard is under the General folder, then the rule is linked to the General Alerting folder, and the rule inherits the default permissions.

Note: Since there is no Keep Last State option for [No Data]({{< relref "./alerting-rules/create-grafana-managed-rule/#no-data--error-handling" >}}) in Grafana alerting, this option becomes NoData during the legacy rules migration. Option "Keep Last State" for [Error handling]({{< relref "./alerting-rules/create-grafana-managed-rule/#no-data--error-handling" >}}) is migrated to a new option Error. To match the behavior of the Keep Last State, in both cases, during the migration Grafana automatically creates a [silence]({{< relref "./silences.md" >}}) for each alert rule with a duration of 1 year.

Notification channels are migrated to an Alertmanager configuration with the appropriate routes and receivers. Default notification channels are added as contact points to the default route. Notification channels not associated with any Dashboard alert go to the autogen-unlinked-channel-recv route.

Since Hipchat and Sensu notification channels are no longer supported, legacy alerts associated with these channels are not automatically migrated to Grafana alerting. Assign the legacy alerts to a supported notification channel so that you continue to receive notifications for those alerts. Silences (expiring after one year) are created for all paused dashboard alerts.

Disable Grafana alerts

To disable Grafana alerts and enable legacy dashboard alerts:

  1. In your custom configuration file ($WORKING_DIR/conf/custom.ini), go to the [Grafana alerting]({{< relref "../administration/configuration.md#unified_alerting" >}}) section.
  2. Set the enabled property to false.
  3. For [legacy dashboard alerting]({{< relref "../administration/configuration.md#alerting" >}}), set the enabled flag to true.
  4. Restart Grafana for the configuration changes to take effect.

Note: Switching from one flavor of alerting to another can result in data loss. This is applicable to the fresh installation as well as upgraded setups.