Skip to content

Conversation

@kallie-liu
Copy link
Contributor

@kallie-liu kallie-liu commented Jan 6, 2026

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

@kallie-liu kallie-liu changed the title New google chat link Incident Response: Google Chat space creation Jan 7, 2026
@kallie-liu kallie-liu marked this pull request as ready for review January 7, 2026 21:09
@kallie-liu kallie-liu requested a review from a team as a code owner January 7, 2026 21:09
@git-thuerk-done git-thuerk-done added the editorial review Waiting on a more in-depth review label Jan 7, 2026
@git-thuerk-done
Copy link
Contributor

Thanks @kallie-liu ! I have created an editorial card for someone on our team to review further.

@valerie-is-amazing2 valerie-is-amazing2 self-requested a review January 7, 2026 21:51
Copy link
Contributor

@valerie-is-amazing2 valerie-is-amazing2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good from the incident app team side!

@janine-c janine-c self-assigned this Jan 8, 2026
Copy link
Contributor

@janine-c janine-c left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, Kallie! I left some comments and suggestions - let me know if you want to chat about any of it or if you'd like any help. And feel free to tag me for final approval!


## Overview

The Google Chat integration for Datadog Incident Management connects your incident response workflows directly to Google Chat by automatically creating Google Chat spaces for collaboration when Datadog incidents are declared.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Google Chat integration for Datadog Incident Management connects your incident response workflows directly to Google Chat by automatically creating Google Chat spaces for collaboration when Datadog incidents are declared.
The Google Chat integration for Datadog Incident Management connects your incident response workflows directly to Google Chat. When your team declares a Datadog incident, the integration automatically creates a Google Chat space for collaboration.

This sentence was long and a bit difficult to follow, so I tried breaking it up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

{{< whatsnext desc="Set up and use the following integrations within the context of Datadog Incident Management:">}}
{{< nextlink href="/incident_response/incident_management/integrations/slack" >}}Slack{{< /nextlink >}}
{{< nextlink href="/incident_response/incident_management/integrations/microsoft_teams" >}}Microsoft Teams{{< /nextlink >}}
{{< nextlink href="/incident_response/incident_management/integrations/google_chat" >}}Google Chat{{< /nextlink >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, added!


Install the integration through the [Google Chat Integration tile][1]. A Google Workspace admin must configure delegated user permissions and set up a target audience and add that to the integration tile. For more information, see the [Google Chat integration][2] documentation.

After the integration is installed, navigate to [**Incidents** > **Settings** > **Integrations**][3] to enable Google Chat features for Incident Management.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After the integration is installed, navigate to [**Incidents** > **Settings** > **Integrations**][3] to enable Google Chat features for Incident Management.

This is pretty vague (which features? How do you do it?), and it's confusing that the click steps are different from the one in the next section, even though the link is the same. Because you go into these details in the next section, I think you can go ahead and remove this! It's a prerequisites section, so I think users generally understand that there's more to do.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

Comment on lines 29 to 45
To use incident spaces, go to **[Incident Response > Incident Management > Settings > Integrations][3]** and enable **Automatically create Google Chat spaces for incidents**.

1. Select an Organization from the dropdown. If you don't see any options, reach out to Google Workspace administrator to connect your Google organization to Datadog.
2. Select a Target Audience from the dropdown. "Default" is the default target audience set by your Google Workspace administrator, which could be a private or public target audience group. Reach out to your Google Workspace administrator if this is unclear.

3. The **channel name template** you define determines how Datadog names the incident spaces it creates. The following variables are available in channel name templates:

* `{{public_id}}`: Incident's numeric ID
* `{{title}}`: Incident's title
* `{{created}}`: Incident's creation date in format MM_DD_YYYY
* `{{yyyy}}`: Incident's four-digit creation year
* `{{mm}}`: Incident's two-digit creation month
* `{{dd}}`: Incident's two-digit creation day of month
* `{{severity}}`: Incident's severity
* `{{random_adjective}}`: Random adjective
* `{{random_noun}}`: Random noun
* `{{slug}}`: Slug (when slug source is set to 'servicenow', this will display the ServiceNow record number)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To use incident spaces, go to **[Incident Response > Incident Management > Settings > Integrations][3]** and enable **Automatically create Google Chat spaces for incidents**.
1. Select an Organization from the dropdown. If you don't see any options, reach out to Google Workspace administrator to connect your Google organization to Datadog.
2. Select a Target Audience from the dropdown. "Default" is the default target audience set by your Google Workspace administrator, which could be a private or public target audience group. Reach out to your Google Workspace administrator if this is unclear.
3. The **channel name template** you define determines how Datadog names the incident spaces it creates. The following variables are available in channel name templates:
* `{{public_id}}`: Incident's numeric ID
* `{{title}}`: Incident's title
* `{{created}}`: Incident's creation date in format MM_DD_YYYY
* `{{yyyy}}`: Incident's four-digit creation year
* `{{mm}}`: Incident's two-digit creation month
* `{{dd}}`: Incident's two-digit creation day of month
* `{{severity}}`: Incident's severity
* `{{random_adjective}}`: Random adjective
* `{{random_noun}}`: Random noun
* `{{slug}}`: Slug (when slug source is set to 'servicenow', this will display the ServiceNow record number)
To use incident spaces:
1. In Datadog, go to **[Incident Response > Incident Management > Settings > Integrations][3]** and enable **Automatically create Google Chat spaces for incidents**.
2. Select an **Organization** from the dropdown. If you don't see any options, reach out to your Google Workspace administrator to connect your Google organization to Datadog.
3. Select a **Target Audience** from the dropdown. **Default** is the default target audience set by your Google Workspace administrator, which could be a private or public target audience group. Reach out to your Google Workspace administrator if this is unclear.
4. The **Channel Name Template** you define determines how Datadog names the incident spaces it creates. The following variables are available in channel name templates:
* `{{public_id}}`: Incident's numeric ID
* `{{title}}`: Incident's title
* `{{created}}`: Incident's creation date in format `MM_DD_YYYY`
* `{{yyyy}}`: Incident's four-digit creation year
* `{{mm}}`: Incident's two-digit creation month
* `{{dd}}`: Incident's two-digit creation day of month
* `{{severity}}`: Incident's severity
* `{{random_adjective}}`: Random adjective
* `{{random_noun}}`: Random noun
* `{{slug}}`: Slug (set to `servicenow` to display the ServiceNow record number)

A bunch of suggestions for readability and formatting. I can't see the UI, so feel free to revert anything that isn't accurate!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed!

Copy link
Contributor

@janine-c janine-c left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beautiful, thanks again for taking a look at these so quickly! Just some tiny things left (including a link that I wanted to check works for you), and then we're good to merge 🎉

kallie-liu and others added 2 commits January 8, 2026 14:32
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
@janine-c janine-c merged commit 40c4489 into master Jan 8, 2026
19 checks passed
@janine-c janine-c deleted the kallie.liu/google-chat-docs branch January 8, 2026 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

editorial review Waiting on a more in-depth review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants