Google Workspace integration for Grafana Incident
Grafana Incident integrates with Google Workspace to reduce the number of administrative tasks associated with incident response. Automatically link Google Meet meetings and Google Drive files directly to an incident so you and your team can focus on incident response without interruption.
Before you begin
The Google Workspace integration requires access to your Google Calendar and Drive. We only have access to resources created by Grafana Incident.
For more information, refer to What data is required? in the last section of this document.
Install Google Workspace integration for Grafana Incident
- Click Incidents in the left-side menu.
- Click Integrations.
- Click the Google Workspace tile and then Sign in with Google.
- Once you’re redirected to authenticate with Google, enter your Google credentials associated with the account you wish to connect to Grafana Incident.
After you’ve authenticated with Google, we’ll:
- Create a new Google Calendar for Grafana Incident to use for incident events
- Create a new Google Drive folder to store incident documents
The links to these resources are included in the integration details page.
Configure actions
Save your team the extra steps of manually generating a meeting or creating an incident document. Configure actions to automatically create a Google Meet meeting or Google Drive document for every incident.
Configure action to create a Google Meet meeting
Grafana Incident will automatically create a Google calendar event and a Google Meet meeting when an incident is declared.
- From the Google Workspace integration, click Run when an event fires bellow the Create a Google Calendar event with a meeting action.
- Specify that the action should run when an incident is declared.
- Click Add event action.
After the action is configured, a link to Join Google Meet is automatically included when you declare an incident.
Configure action to create a Google Drive file
Grafana Incident will automatically copy a Google Docs template and attach it to your incident when one is declared. We provided a PIR (Post-Incident Review) as an example, but this template can be edited to fit your goals. A new Google Doc using this template is created when this action runs.
- From the Google integration, click Run when an event fires bellow the New Google Doc from template action.
- Specify that the action should run when an incident is declared.
- Click Add event action.
Grafana Incident automatically includes a link to Open Google Docs when an incident is declared.
PIR Template Variables
Note
Template Variables are currently an Experimental feature. Grafana Labs offers support on a best-effort basis, and there might be breaking changes before the feature is generally available.
Customize your PIR template using template variables to dynamically update your PIR document with real-time incident data. This allows for better documentation and accurate analysis of incidents, enabling your team to learn and improve from past experiences.
Add variables to PIR template
To incorporate template variables into your PIR document, enclose the desired variables within curly braces. For instance, incident.title
becomes {{ incident.title }}
.
Additionally, you can introduce new variables to an existing PIR document even after its creation from the template. Any added variables will be automatically recognized and updated as the incident progresses.
To begin utilizing template variables, follow these steps:
- Populate the PIR template with supported variables, such as
{{ incident.title }}
. - Declare an incident with Grafana Incident.
- Access the generated PIR document.
- Make relevant modifications to the incident details, such as renaming.
- Confirm the latest incident data is reflected in the PIR document.
- If Slack-related variables (
{{ incident.slack-url }}
or{{ incident.url }}
) are included, they will appear as clickable links.
Supported Variables
The following variables are currently supported:
Variable | Description | Example |
---|---|---|
incident.url | Direct link to the incident in Grafana Incident | |
incident.title | The up-to-date incident title | Coffee Machine is OOMing |
incident.date | Date (YYYY-MM-DD ) the incident was declared | 2024-01-01 |
incident.author | The name of the user declaring the incident | John Smith |
incident.summary | The summary as entered when resolving the incident. | |
incident.slack-url | Direct Link to the Slack Channel once available. | |
incident.status | Incident status | active or resolved |
incident.severity | Incident severity | pending , minor , major , or critical |
incident.start | Time the incident actually started | 2024-01-01T01:10:10.0Z (RFC3339 ) |
incident.declared | Time the incident was declared | 2024-01-01T01:10:10.0Z (RFC3339 ) |
incident.resolved | Time the incident was marked as resolved | 2024-01-01T01:10:10.0Z (RFC3339 ) |
incident.end | Time the incident actually ended | 2024-01-01T01:10:10.0Z (RFC3339 ) |
What data is required?
We respect your privacy, for that reason, Grafana Incident pull the minimum necessary data required to deliver the features of this integration. We only have access to the resources (files, calendars, etc) that are created by the integration. The API is used to:
- Create a calendar event for each incident in order to create a Google Meet session (optional)
- Copy a Google Doc (usually a template) for each incident (optional)
Was this page helpful?
Related resources from Grafana Labs
![Getting started with the Grafana LGTM Stack](/static/assets/featured/getting-started-with-grafana-lgtm-stack-amer_featured.png?w=200 200w, /static/assets/featured/getting-started-with-grafana-lgtm-stack-amer_featured.png?w=400 400w)
![Intro to Kubernetes monitoring in Grafana Cloud](/media/webinar/Screenshot-2024-02-12-at-4.09.30-PM.png?w=200 200w, /media/webinar/Screenshot-2024-02-12-at-4.09.30-PM.png?w=400 400w)
![Building advanced Grafana dashboards](/media/webinar/AMER_buildadv_notxt.png?w=200 200w, /media/webinar/AMER_buildadv_notxt.png?w=400 400w)