-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Incident Response: Google Chat space creation #33690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Preview links (active after the
|
|
Thanks @kallie-liu ! I have created an editorial card for someone on our team to review further. |
valerie-is-amazing2
left a comment
There was a problem hiding this 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!
There was a problem hiding this 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
There was a problem hiding this comment.
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 >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we also need a link on this page? https://docs.datadoghq.com/incident_response/incident_management/incident_settings/integrations/
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
| 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) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed!
janine-c
left a comment
There was a problem hiding this 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 🎉
content/en/incident_response/incident_management/integrations/google_chat.md
Outdated
Show resolved
Hide resolved
content/en/incident_response/incident_management/integrations/google_chat.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Janine Chan <[email protected]>
Co-authored-by: Janine Chan <[email protected]>
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
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