2.2 KiB
aliases | description | title | weight | |||
---|---|---|---|---|---|---|
|
Disable Grafana alerts | Opt-out of Grafana alerting | 113 |
Opt-out to Grafana alerting in OSS
This topic discusses how to disable Grafana alerting and migrate to legacy dashboard alerting. It also provides guidance on how to enable Grafana alerting once you are ready to migrate to Grafana alerting.
Note: This topic is only relevant for OSS and Enterprise customers. Contact customer support to enable or disable Grafana alerting for your Grafana Cloud stack.
Before you begin
We recommend that you backup Grafana's database. If you are using PostgreSQL as the backend database, then the minimum required version is 9.5.
Opt-out of Grafana alerts
To opt-out of Grafana alerts and roll back to legacy dashboard alerting:
- In your custom configuration file ($WORKING_DIR/conf/custom.ini), go to the [Grafana alerting]({{< relref "../../administration/configuration.md#unified_alerting" >}}) section.
- Set the
enabled
property tofalse
. - For [legacy dashboard alerting]({{< relref "../../administration/configuration.md#alerting" >}}), set the
enabled
flag totrue
. - Restart Grafana for the configuration changes to take effect.
Note: Rolling back from Grafana to legacy alerting can result in data loss. This is applicable to the fresh installation as well as upgraded setups.
Opt-in to Grafana alerting
When you are ready to make the switch, the following procedure will help you migrate to Grafana alerting.
To opt-in to Grafana alerts:
- In your custom configuration file ($WORKING_DIR/conf/custom.ini), go to the [unified alerts]({{< relref "../../administration/configuration.md#unified_alerting" >}}) section.
- Set the
enabled
property totrue
. - Next, for [legacy dashboard alerting]({{< relref "../../administration/configuration.md#alerting" >}}), set the
enabled
flag tofalse
. - Restart Grafana for the configuration changes to take effect.
Note: The
ngalert
toggle previously used to enable or disable Grafana alerting is no longer available.