|
|
|
|
@@ -13,44 +13,141 @@ weight: 150
|
|
|
|
|
|
|
|
|
|
# Upgrade Alerting
|
|
|
|
|
|
|
|
|
|
Grafana Alerting is enabled by default for new installations or existing installations whether or not legacy alerting is configured.
|
|
|
|
|
|
|
|
|
|
{{% admonition type="note" %}}
|
|
|
|
|
When upgrading, your dashboard alerts are migrated to a new format. This migration can be rolled back easily by opting out. If you have any questions regarding this migration, please contact us.
|
|
|
|
|
Legacy alerting will be removed in Grafana v11.0.0. We recommend that you upgrade to Grafana Alerting as soon as possible.
|
|
|
|
|
For more information, refer to [Legacy alerting deprecation]({{< relref "./legacy-alerting-deprecation" >}}).
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
Existing installations that do not use legacy alerting will have Grafana Alerting enabled by default unless alerting is disabled in the configuration.
|
|
|
|
|
Grafana provides two methods for a seamless automatic upgrade of legacy alert rules and notification channels to Grafana Alerting:
|
|
|
|
|
|
|
|
|
|
Likewise, existing installations that use legacy alerting will be automatically upgraded to Grafana Alerting unless you have opted out of Grafana Alerting before migration takes place. During the upgrade, legacy alerts are migrated to the new alerts type and no alerts or alerting data are lost.
|
|
|
|
|
|
|
|
|
|
Once the upgrade has taken place, you still have the option to roll back to legacy alerting. However, we do not recommend choosing this option. If you do choose to roll back, Grafana will restore your alerts to the alerts you had at the point in time when the upgrade took place.
|
|
|
|
|
1. **Upgrade with Preview** (Recommended): Offers a safe and controlled preview environment where you can review and adjust your upgraded alerts before fully enabling Grafana Alerting.
|
|
|
|
|
2. **Simple Upgrade**: One-step upgrade method for specific needs where a preview environment is not essential.
|
|
|
|
|
|
|
|
|
|
{{% admonition type="note" %}}
|
|
|
|
|
Cloud customers, who do not want to upgrade to Grafana Alerting, should contact customer support.
|
|
|
|
|
When upgrading with either method, your legacy dashboard alerts and notification channels are copied to a new format. This is non-destructive and can be [rolled back easily]({{< relref "#rolling-back-to-legacy-alerting" >}}).
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
If you have opted out or rolled back, you can always choose to opt in to Grafana Alerting at a later point in time.
|
|
|
|
|
## Key Considerations
|
|
|
|
|
|
|
|
|
|
The following table provides details on the upgrade for Cloud, Enterprise, and OSS installations and the new Grafana Alerting UI.
|
|
|
|
|
| Feature | Upgrade with Preview | Simple Upgrade |
|
|
|
|
|
| --------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------- |
|
|
|
|
|
| **Safety and Control** | ☑️ Preview environment for review and adjustment | ❌ No preview, potential for unexpected issues |
|
|
|
|
|
| **User Experience** | ☑️ Seamless transition by handling issues early | ❌ Possible disruption during upgrade |
|
|
|
|
|
| **Granular Control** | ☑️ Re-upgrade specific resources after resolving errors | ❌ All or nothing upgrade, manual error correction |
|
|
|
|
|
| **Stakeholder Involvement** | ☑️ Collaboration and review of adjusted alerts | ❌ Review only available after upgrade |
|
|
|
|
|
| **Provisioning Support** | ☑️ Configure new as-code before upgrading, simultaneous provisioning | ❌ No built-in provisioning support |
|
|
|
|
|
| **Simplicity** | ❌ May take longer to complete | ☑️ Fast, one-step process |
|
|
|
|
|
| **Technical Requirements** | Feature flag enabled, Grafana v10.3.0+ | Grafana v9.0.0+ |
|
|
|
|
|
| **Suited for:** | ☑️ Complex setups, risk-averse environments, collaborative teams, heavy as-code use | ☑️ Simple setups, testing environments, large fleets |
|
|
|
|
|
|
|
|
|
|
| Grafana instance upgraded to 9.0 | |
|
|
|
|
|
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
|
|
|
| Cloud | Existing Cloud installations with legacy dashboard alerting will have two alerting icons in the left navigation panel - the old alerting plugin icon and the new Grafana Alerting icon. During upgrade, existing alerts from the Cloud alerting plugin are migrated to Grafana Alerting. Once migration is complete, you can access and manage the older alerts from the new alerting Grafana Alerting icon in the navigation panel. The (older) Cloud alerting plugin is uninstalled from your cloud instance. Contact customer support if you **do not wish** to migrate to Grafana Alerting for your Cloud stack. If you choose to use legacy alerting, use the You will see the new Grafana Alerting icon as well as the old Cloud alerting plugin in the left navigation panel. |
|
|
|
|
|
| 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 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 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. |
|
|
|
|
|
## Upgrade with Preview (Recommended)
|
|
|
|
|
|
|
|
|
|
> **Note:** Starting with v9.0, legacy alerting is deprecated and will be removed in a future release.
|
|
|
|
|
### Prerequisites
|
|
|
|
|
|
|
|
|
|
## Opt out
|
|
|
|
|
- Grafana `v10.3.0 or later`.
|
|
|
|
|
- Grafana administrator access.
|
|
|
|
|
- Enable `alertingPreviewUpgrade` [feature toggle]({{< relref "../../../setup-grafana/configure-grafana/feature-toggles" >}}).
|
|
|
|
|
|
|
|
|
|
You can opt out of Grafana Alerting at any time and switch to using legacy alerting. Alternatively, you can opt out of using alerting in its entirety.
|
|
|
|
|
### Suited for
|
|
|
|
|
|
|
|
|
|
## Stay on legacy alerting
|
|
|
|
|
- **Complex setups**: Large deployments with intricate alert rules and notification channels.
|
|
|
|
|
- **Risk-averse environments**: Situations where minimizing disruption and ensuring a smooth transition are critical.
|
|
|
|
|
- **Collaborative teams**: Projects where feedback and review from stakeholders are valuable.
|
|
|
|
|
- **Heavy as-code use**: Deployments with large or complex as-code configurations.
|
|
|
|
|
|
|
|
|
|
When upgrading to Grafana > 9.0, existing installations that use legacy alerting are automatically upgraded to Grafana Alerting unless you have opted-out of Grafana Alerting before migration takes place. During the upgrade, legacy alerts are migrated to the new alerts type and no alerts or alerting data are lost. To keep using legacy alerting and deactivate Grafana Alerting:
|
|
|
|
|
### Overview
|
|
|
|
|
|
|
|
|
|
1. Go to your custom configuration file ($WORKING_DIR/conf/custom.ini).
|
|
|
|
|
2. Enter the following in your configuration:
|
|
|
|
|
In **Alerts & IRM**, the **Alerting** section provides a preview of Grafana Alerting where you can review and modify your upgraded alerts before finalizing the upgrade.
|
|
|
|
|
|
|
|
|
|
In the **Alerting (legacy) -> Alerting upgrade** section, you can initiate the process to automatically upgrade your existing alert rules and notification channels, and view a summary of the upgrade to Grafana Alerting.
|
|
|
|
|
|
|
|
|
|
Finalize your upgrade by restarting Grafana with the `[unified_alerting]` section enabled in your configuration.
|
|
|
|
|
|
|
|
|
|
{{% admonition type="note" %}}
|
|
|
|
|
Alerts generated by the new alerting system are visible in the **Alerting** section of the navigation panel but are not active until the upgrade is finalized.
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
### To upgrade with preview, complete the following steps.
|
|
|
|
|
|
|
|
|
|
1. **Preview the Upgrade**:
|
|
|
|
|
- **Initiate the process**: Access the upgrade functionality within Grafana by visiting the **Alerting upgrade** page in the **Alerting (legacy)** section of the navigation panel. Click on "Preview upgrade" to initiate the process. This will automatically upgrade your existing alert rules and notification channels to the new Grafana Alerting system.
|
|
|
|
|
- **Review the summary table:** Review the detailed table outlining how your existing alert rules and notification channels were mapped to resources in the new Grafana Alerting system.
|
|
|
|
|
2. **Investigate and Resolve Errors**:
|
|
|
|
|
- **Identify errors**: Carefully examine the previewed upgrade:
|
|
|
|
|
- Any alert rules or notification channels that couldn't be automatically upgraded will be highlighted with error indicators.
|
|
|
|
|
- New or removed alert rules and notification channels will be highlighted with warning indicators.
|
|
|
|
|
- **Address errors**: You have two options to resolve these issues:
|
|
|
|
|
- **Fix legacy issues**: If possible, address the problems within your legacy alerting setup and attempt to upgrade the specific resource again.
|
|
|
|
|
- **Create new resources**: If fixing legacy issues isn't viable, create new alert rules, notification policies, or contact points manually within the new Grafana Alerting system to replace the problematic ones.
|
|
|
|
|
3. **Update As-Code Setup** (Optional):
|
|
|
|
|
- **Export upgraded resources**: If you use provisioning methods to manage alert rules and notification channels, you can export the upgraded versions to generate provisioning files compatible with Grafana Alerting.
|
|
|
|
|
- **Test new provisioning definitions**: Ensure your as-code setup aligns with the new system before completing the upgrade process. Both legacy and Grafana Alerting alerts can be provisioned simultaneously to facilitate a smooth transition.
|
|
|
|
|
4. **Finalize the Upgrade**:
|
|
|
|
|
- **Contact your Grafana server administrator**: Once you're confident in the state of your previewed upgrade, request to [enable Grafana Alerting]({{< relref "#enable-grafana-alerting" >}}).
|
|
|
|
|
- **Continued use for upgraded organizations**: Organizations that have already completed the preview upgrade will seamlessly continue using their configured setup.
|
|
|
|
|
- **Automatic upgrade for others**: Organizations that haven't initiated the upgrade with preview process will undergo the traditional automatic upgrade during this restart.
|
|
|
|
|
- **Address issues before restart**: Exercise caution, as Grafana will not start if any traditional automatic upgrades encounter errors. Ensure all potential issues are resolved before initiating this step.
|
|
|
|
|
|
|
|
|
|
## Simple Upgrade
|
|
|
|
|
|
|
|
|
|
### Prerequisites
|
|
|
|
|
|
|
|
|
|
- Grafana `v9.0.0 or later` (more recent versions are recommended).
|
|
|
|
|
|
|
|
|
|
### Suited for
|
|
|
|
|
|
|
|
|
|
- **Simple setups**: Limited number of alerts and channels with minimal complexity.
|
|
|
|
|
- **Testing environments**: Where a quick upgrade without a preview is sufficient.
|
|
|
|
|
- **Large fleets**: Where manually reviewing each instance is not feasible.
|
|
|
|
|
|
|
|
|
|
### Overview
|
|
|
|
|
|
|
|
|
|
While we recommend the **Upgrade with Preview** method for its enhanced safety and control, the **Simple Upgrade Method** exists for specific situations where a preview environment is not essential. For example, if you have a large fleet of Grafana instances and want to upgrade them all without the need to review and adjust each one individually.
|
|
|
|
|
|
|
|
|
|
Configure your Grafana instance to enable Grafana Alerting and disable legacy alerting. Then restart Grafana to automatically upgrade your existing alert rules and notification channels to the new Grafana Alerting system.
|
|
|
|
|
|
|
|
|
|
Once Grafana Alerting is enabled, you can review and adjust your upgraded alerts in the **Alerting** section of the navigation panel as well as export them for as-code setup.
|
|
|
|
|
|
|
|
|
|
### To perform the simple upgrade, complete the following steps.
|
|
|
|
|
|
|
|
|
|
{{% admonition type="note" %}}
|
|
|
|
|
Any errors encountered during the upgrade process will fail the upgrade and prevent Grafana from starting. If this occurs, you can [roll back to legacy alerting]({{< relref "#rolling-back-to-legacy-alerting" >}}).
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
1. **Upgrade to Grafana Alerting**:
|
|
|
|
|
- **Enable Grafana Alerting**: [Modify custom configuration file]({{< relref "#enable-grafana-alerting" >}}).
|
|
|
|
|
- **Restart Grafana**: Restart Grafana for the configuration changes to take effect. Grafana will automatically upgrade your existing alert rules and notification channels to the new Grafana Alerting system.
|
|
|
|
|
2. **Review and Adjust Upgraded Alerts**:
|
|
|
|
|
- **Review the upgraded alerts**: Go to the `Alerting` section of the navigation panel to review the upgraded alerts.
|
|
|
|
|
- **Export upgraded resources**: If you use provisioning methods to manage alert rules and notification channels, you can export the upgraded versions to generate provisioning files compatible with Grafana Alerting.
|
|
|
|
|
|
|
|
|
|
## Additional Information
|
|
|
|
|
|
|
|
|
|
### Enable Grafana Alerting
|
|
|
|
|
|
|
|
|
|
Go to your custom configuration file ($WORKING_DIR/conf/custom.ini) and enter the following in your configuration:
|
|
|
|
|
|
|
|
|
|
```toml
|
|
|
|
|
[alerting]
|
|
|
|
|
enabled = false
|
|
|
|
|
|
|
|
|
|
[unified_alerting]
|
|
|
|
|
enabled = true
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
{{% admonition type="note" %}}
|
|
|
|
|
If you have existing legacy alerts we advise using the [Upgrade with Preview]({{< relref "#upgrade-with-preview-recommended" >}}) method first to ensure a smooth transition. Any organizations that have not completed the preview upgrade will automatically undergo the simple upgrade during the next restart.
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
### Rolling back to legacy alerting
|
|
|
|
|
|
|
|
|
|
{{% admonition type="note" %}}
|
|
|
|
|
For Grafana Cloud, contact customer support to enable or disable Grafana Alerting for your stack.
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
If you have upgraded to Grafana Alerting and want to roll back to legacy alerting, you can do so by disabling Grafana Alerting and re-enabling legacy alerting.
|
|
|
|
|
|
|
|
|
|
Go to your custom configuration file ($WORKING_DIR/conf/custom.ini) and enter the following in your configuration:
|
|
|
|
|
|
|
|
|
|
```toml
|
|
|
|
|
[alerting]
|
|
|
|
|
@@ -60,48 +157,7 @@ enabled = true
|
|
|
|
|
enabled = false
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Installations that have been migrated to Grafana Alerting can roll back to legacy alerting at any time.
|
|
|
|
|
|
|
|
|
|
{{% admonition type="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.
|
|
|
|
|
{{% /admonition %}}
|
|
|
|
|
|
|
|
|
|
The `ngalert` toggle previously used to enable or disable Grafana Alerting is no longer available.
|
|
|
|
|
|
|
|
|
|
## Deactivate alerting
|
|
|
|
|
|
|
|
|
|
You can deactivate both Grafana Alerting and legacy alerting in Grafana.
|
|
|
|
|
|
|
|
|
|
1. Go to your custom configuration file ($WORKING_DIR/conf/custom.ini).
|
|
|
|
|
1. Enter the following in your configuration:
|
|
|
|
|
|
|
|
|
|
```toml
|
|
|
|
|
[alerting]
|
|
|
|
|
enabled = false
|
|
|
|
|
|
|
|
|
|
[unified_alerting]
|
|
|
|
|
enabled = false
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
3. Restart Grafana for the configuration changes to take effect.
|
|
|
|
|
|
|
|
|
|
If you want to turn alerting back on, you can remove both flags to enable Grafana Alerting.
|
|
|
|
|
|
|
|
|
|
## Roll back
|
|
|
|
|
|
|
|
|
|
Once the upgrade has taken place, you still have the option to roll back to legacy alerting. If you choose to roll back, Grafana will restore your alerts to the alerts you had at the point in time when the upgrade took place.
|
|
|
|
|
|
|
|
|
|
To roll back to legacy alerting, enter the following in your configuration:
|
|
|
|
|
|
|
|
|
|
```toml
|
|
|
|
|
[alerting]
|
|
|
|
|
enabled = true
|
|
|
|
|
|
|
|
|
|
[unified_alerting]
|
|
|
|
|
enabled = false
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
> **Note**: The next time you upgrade to Grafana Alerting, Grafana will restore your Grafana Alerting alerts and configuration to those you had before rolling back.
|
|
|
|
|
This action is non-destructive. You can seamlessly switch between legacy alerting and Grafana Alerting at any time without losing any data. However, the upgrade process will only be performed once. If you have opted out of Grafana Alerting and then opt in again, Grafana will not perform the upgrade again.
|
|
|
|
|
|
|
|
|
|
If, after rolling back, you wish to delete any existing Grafana Alerting configuration and upgrade your legacy alerting configuration again from scratch, you can enable the `clean_upgrade` option:
|
|
|
|
|
|
|
|
|
|
@@ -110,52 +166,31 @@ If, after rolling back, you wish to delete any existing Grafana Alerting configu
|
|
|
|
|
clean_upgrade = true
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Opt in
|
|
|
|
|
### Differences and limitations
|
|
|
|
|
|
|
|
|
|
If you have previously disabled alerting in Grafana, or opted out of Grafana Alerting and have decided that you would now like to use Grafana Alerting, you can choose to opt in at any time.
|
|
|
|
|
|
|
|
|
|
If you have been using legacy alerting up until now your existing alerts will be migrated to the new alerts type and no alerts or alerting data are lost. Even if you choose to opt in to Grafana Alerting, you can roll back to legacy alerting at any time.
|
|
|
|
|
|
|
|
|
|
To opt in to Grafana Alerting, enter the following in your configuration:
|
|
|
|
|
|
|
|
|
|
```toml
|
|
|
|
|
[alerting]
|
|
|
|
|
enabled = false
|
|
|
|
|
|
|
|
|
|
[unified_alerting]
|
|
|
|
|
enabled = true
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Differences and limitations
|
|
|
|
|
|
|
|
|
|
There are some differences between Grafana Alerting and legacy dashboard alerts, and a number of features that are no
|
|
|
|
|
longer supported.
|
|
|
|
|
There are some differences between Grafana Alerting and legacy dashboard alerts, and a number of features that are no longer supported.
|
|
|
|
|
|
|
|
|
|
**Differences**
|
|
|
|
|
|
|
|
|
|
1. When Grafana Alerting is enabled or upgraded to Grafana 9.0 or later, 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 any new alerts.
|
|
|
|
|
This topic explains how legacy dashboard alerts are migrated and some limitations of the migration.
|
|
|
|
|
1. Read and write access to legacy dashboard alerts are governed by the dashboard permissions (including the inherited permissions from the folder) while Grafana alerts are governed by the permissions of the folder only. During the upgrade, an alert rule might be moved to a different folder to match the permissions of the dashboard. The following rules apply:
|
|
|
|
|
|
|
|
|
|
1. 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 the inherited dashboard permissions are different from the permissions of the folder, then the rule is moved to a new folder named after the original: `<Original folder name> - <Permission Hash>`.
|
|
|
|
|
- If the inherited dashboard permissions are the same as the permissions of the folder, then the rule is moved to the original folder.
|
|
|
|
|
- If the dashboard is in the `General` or `Dashboards` folder (i.e. no folder), then the rule is moved to a new `General Alerting - <Permission Hash>` folder.
|
|
|
|
|
|
|
|
|
|
- If there are dashboard permissions, a folder named `Migrated {"dashboardUid": "UID", "panelId": 1, "alertId": 1}` is created to match the permissions of the dashboard (including the inherited permissions from the folder).
|
|
|
|
|
- If there are no dashboard permissions and the dashboard is in a folder, then the rule is linked to this folder and inherits its permissions.
|
|
|
|
|
- If there are no dashboard permissions and the dashboard is in the General folder, then the rule is linked to the `General Alerting` folder and the rule inherits the default permissions.
|
|
|
|
|
1. `NoData` and `Error` settings are upgraded as is to the corresponding settings in Grafana Alerting, except in two situations:
|
|
|
|
|
|
|
|
|
|
1. `NoData` and `Error` settings are migrated as is to the corresponding settings in Grafana Alerting, except in two situations:
|
|
|
|
|
- As there is no `Keep Last State` option in Grafana Alerting, this option becomes either [`NoData` or `Error`](/docs/sources/alerting/alerting-rules/create-grafana-managed-rule/#configure-no-data-and-error-handling). If using the `Simple Upgrade Method` Grafana automatically creates a 1 year silence for each alert rule with this configuration. If the alert evaluation returns no data or fails (error or timeout), then it creates a [special alert](/docs/sources/alerting/fundamentals/alert-rules/state-and-health/#special-alerts-for-nodata-and-error), which will be silenced by the silence created during the upgrade.
|
|
|
|
|
- Due to lack of validation, legacy alert rules imported via JSON or provisioned along with dashboards can contain arbitrary values for [`NoData` or `Error`](/docs/sources/alerting/alerting-rules/create-grafana-managed-rule/#configure-no-data-and-error-handling). In this situation, Grafana will use the default setting: `NoData` for No data, and `Error` for Error.
|
|
|
|
|
|
|
|
|
|
3.1. As there is no `Keep Last State` option in Grafana Alerting, this option becomes either [`NoData` or `Error`](/docs/sources/alerting/alerting-rules/create-grafana-managed-rule/#configure-no-data-and-error-handling). To match the behavior of the `Keep Last State` as closely as possible during the migration Grafana automatically creates a silence for each alert rule with a duration of 1 year. If the alert evaluation returns no data or fails (error or timeout), then it creates a [special alert](/docs/sources/alerting/fundamentals/alert-rules/state-and-health/#special-alerts-for-nodata-and-error), which will be silenced by the silence created during the migration.
|
|
|
|
|
|
|
|
|
|
3.2. Due to lack of validation, legacy alert rules imported via JSON or provisioned along with dashboards can contain arbitrary values for [`NoData` or `Error`](/docs/sources/alerting/alerting-rules/create-grafana-managed-rule/#configure-no-data-and-error-handling). In this situation, Grafana will use the default setting: `NoData` for No data, and `Error` for Error.
|
|
|
|
|
|
|
|
|
|
1. 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.
|
|
|
|
|
1. Notification channels are upgraded to an Alertmanager configuration with the appropriate routes and receivers.
|
|
|
|
|
|
|
|
|
|
1. Unlike legacy dashboard alerts where images in notifications are enabled per contact point, images in notifications for Grafana Alerting must be enabled in the Grafana configuration, either in the configuration file or environment variables, and are enabled for either all or no contact points.
|
|
|
|
|
|
|
|
|
|
1. The JSON format for webhook notifications has changed in Grafana Alerting and uses the format from [Prometheus Alertmanager](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config).
|
|
|
|
|
|
|
|
|
|
1. Alerting on Prometheus `Both` type queries is not supported in Grafana Alerting. Existing legacy alerts with `Both` type queries are migrated to Grafana Alerting as alerts with `Range` type queries.
|
|
|
|
|
1. Alerting on Prometheus `Both` type queries is not supported in Grafana Alerting. Existing legacy alerts with `Both` type queries are upgraded to Grafana Alerting as alerts with `Range` type queries.
|
|
|
|
|
|
|
|
|
|
**Limitations**
|
|
|
|
|
|
|
|
|
|
1. 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.
|
|
|
|
|
1. Since `Hipchat` and `Sensu` notification channels are no longer supported, legacy alerts associated with these channels are not automatically upgraded to Grafana Alerting. Assign the legacy alerts to a supported notification channel so that you continue to receive notifications for those alerts.
|
|
|
|
|
|
Matthew Jacobson
GitHub