From ab963a85580aee9d7c7ea2dbb80c94a8e2f9586e Mon Sep 17 00:00:00 2001 From: brendamuir <100768211+brendamuir@users.noreply.github.com> Date: Tue, 12 Sep 2023 19:46:03 +0200 Subject: [PATCH] Alerting docs: quick corrections to oncall integration (#74758) * Alerting docs: quick corrections to oncall integration * corrects spelling errors --- .../manage-contact-points/configure-oncall.md | 22 +++++++++---------- .../angular_deprecation/angular-plugins.md | 2 +- .../http_api/alerting_provisioning.md | 2 +- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/sources/alerting/alerting-rules/manage-contact-points/configure-oncall.md b/docs/sources/alerting/alerting-rules/manage-contact-points/configure-oncall.md index f1612841415..97871967836 100644 --- a/docs/sources/alerting/alerting-rules/manage-contact-points/configure-oncall.md +++ b/docs/sources/alerting/alerting-rules/manage-contact-points/configure-oncall.md @@ -35,27 +35,27 @@ To set up the Grafana OnCall integration using the Grafana Alerting application, 1. Enter a contact point name. 1. From the Integration list, select Grafana OnCall. -{{% admonition type="note" %}} -The Grafana OnCall integration is only available for Grafana Alertmanager. -{{% /admonition %}} + **Note:** -5. Choose whether to add a new OnCall integration or add an existing one. + The Grafana OnCall integration is only available for Grafana Alertmanager. + +1. Choose whether to add a new OnCall integration or add an existing one. - If you add a new one, enter an Integration name. - If you add an existing one, choose from the list of available integrations -6. Click **Save contact point**. +1. Click **Save contact point**. -7. On the Contact points list view page, you can see the contact point with the Grafana OnCall icon. +1. On the Contact points list view page, you can see the contact point with the Grafana OnCall icon. If the integration is not yet being used anywhere in the notification policies tree, it will have **Unused** as its status in the **Health** column. It won’t receive any notifications, because there are no notifications using that integration. -8. Connect your contact point to a notification policy. +1. Connect your contact point to a notification policy. For more information on connecting your contact point to a notification policy, see - [Create notification policy][create-notification-policy] + [Create notification policy][create-notification-policy]. -9. To view your integration in the Grafana OnCall application and set up routes and escalation chains, click the Link next to the integration on the Contact points list view page in the **Type** column. +1. To view your integration in the Grafana OnCall application and set up routes and escalation chains, click the Link next to the integration on the Contact points list view page in the **Type** column. This redirects you to the Grafana OnCall integration page in the Grafana OnCall application. From there, you can add [routes and escalation chains][escalation-chain]. @@ -66,6 +66,6 @@ The Grafana OnCall integration is only available for Grafana Alertmanager. [oncall-integration]: "/docs/grafana/ -> /docs/oncall/latest/integrations/grafana-alerting" [oncall-integration]: "/docs/grafana-cloud/ -> /docs/oncall/latest/integrations/grafana-alerting" -[escalation-chain] "/docs/grafana/ -> /docs/oncall/latest/escalation-chains-and-routes" -[escalation-chain] "/docs/grafana-cloud/ -> /docs/oncall/latest/escalation-chains-and-routes" +[escalation-chain]: "/docs/grafana/ -> /docs/oncall/latest/escalation-chains-and-routes" +[escalation-chain]: "/docs/grafana-cloud/ -> /docs/oncall/latest/escalation-chains-and-routes" {{% /docs/reference %}} diff --git a/docs/sources/developers/angular_deprecation/angular-plugins.md b/docs/sources/developers/angular_deprecation/angular-plugins.md index e0f669a9a9d..3e169dd81ab 100644 --- a/docs/sources/developers/angular_deprecation/angular-plugins.md +++ b/docs/sources/developers/angular_deprecation/angular-plugins.md @@ -640,7 +640,7 @@ Latest Version: 0.7.1 | Signature: Community | Last Updated: 2021 Lack of recent activity in the [project repository](https://github.com/fatcloud/windrose-panel) in the past 4 years suggests project _may_ not be actively maintained. {{% /admonition %}} -> **Migration available - potential alternative:** another plugin exists which provides similar capabilities - [Operato Windrose](https://grafana.com/grafana/plugins/operato-windrose-panel/) +> **Migration available - potential alternative:** another plugin exists which provides similar capabilities - [Operator Windrose](https://grafana.com/grafana/plugins/operato-windrose-panel/) ### [Statusmap](https://grafana.com/grafana/plugins/flant-statusmap-panel/) diff --git a/docs/sources/developers/http_api/alerting_provisioning.md b/docs/sources/developers/http_api/alerting_provisioning.md index a1737c6ef3a..c02a4bb02a4 100644 --- a/docs/sources/developers/http_api/alerting_provisioning.md +++ b/docs/sources/developers/http_api/alerting_provisioning.md @@ -1475,7 +1475,7 @@ Status: Accepted ### RouteExport -> RouteExport is the provisioned file export of definitions.Route. This is needed to hide fields that aren't useable in +> RouteExport is the provisioned file export of definitions.Route. This is needed to hide fields that aren't usable in > provisioning file format. An alternative would be to define a custom MarshalJSON and MarshalYAML that excludes them. **Properties**