9ae442faa6
You can use `ref` URIs in admonitions (or any shortcodes) because they are inline and not subject to the issues noted in the [`admonition` shortcode](https://grafana.com/docs/writers-toolkit/write/shortcodes/#code-shortcode:~:text=to%20core%20understanding.-,WARNING,For%20more%20information%2C%20refer%20to%20Markdown%20Reference%20Links%20in%20Shortcodes.,-Examples). The `ref` URIs perform the same pattern matching as `docs/reference` but don't require the use of reference-style links and the destinations are ordinary (full) URLs that can include version substitution. Unlike `docs/reference`, the implementation doesn't use `relref` so you don't have to be careful with omitting trailing slashes and the links will follow redirects. Documentation: https://grafana.com/docs/writers-toolkit/write/links/#link-from-source-content-thats-used-in-multiple-projects To check the links, refer to the deploy preview in https://github.com/grafana/website/pull/19630. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> --------- Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
49 lines
2 KiB
Markdown
49 lines
2 KiB
Markdown
---
|
|
title: Stackdriver integration for Grafana OnCall
|
|
menuTitle: Stackdriver
|
|
description: Learn how to configure the Stackdriver integration for Grafana OnCall.
|
|
weight: 0
|
|
keywords:
|
|
- OnCall
|
|
- Integrations
|
|
- Alerts
|
|
- Stackdriver
|
|
- Notifications
|
|
labels:
|
|
products:
|
|
- cloud
|
|
canonical: https://grafana.com/docs/oncall/latest/configure/integrations/references/stackdriver
|
|
aliases:
|
|
- /docs/grafana-cloud/alerting-and-irm/oncall/configure/integrations/references/stackdriver
|
|
- /docs/grafana-cloud/alerting-and-irm/oncall/integrations/stackdriver
|
|
- /docs/oncall/latest/integrations/stackdriver/
|
|
- ../integrations/ # /docs/oncall/<ONCALL_VERSION>/configure/integrations/references/stackdriver
|
|
refs:
|
|
user-and-team-management:
|
|
- pattern: /docs/oncall/
|
|
destination: /docs/oncall/<ONCALL_VERSION>/manage/user-and-team-management/
|
|
- pattern: /docs/grafana-cloud/
|
|
destination: /docs/grafana-cloud/alerting-and-irm/oncall/manage/user-and-team-management/
|
|
---
|
|
|
|
# Stackdriver integration for Grafana OnCall
|
|
|
|
{{< admonition type="note" >}}
|
|
This integration is available exclusively on Grafana Cloud.
|
|
{{< /admonition >}}
|
|
|
|
The Stackdriver integration for Grafana OnCall handles ticket events sent from Stackdriver webhooks.
|
|
The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.
|
|
|
|
## Configuring Grafana OnCall to Receive Alerts from Stackdriver
|
|
|
|
1. In the **Integrations** tab, click **+ New integration**.
|
|
2. Select **Stackdriver** from the list of available integrations.
|
|
3. Enter a name and description for the integration, click **Create**
|
|
4. A new page will open with the integration details. Copy the **OnCall Integration URL** from **HTTP Endpoint** section.
|
|
|
|
## Configuring Stackdriver to Send Alerts to Grafana OnCall
|
|
|
|
1. Create a notification channel in Stackdriver by navigating to Workspace Settings -> WEBHOOKS -> Add Webhook **OnCall Integration URL**
|
|
|
|
2. Create and alert in Stackdriver by navigating to Alerting -> Policies -> Add Policy -> Choose Notification Channel using the channel set up in step 1
|