Repository navigation
Update ServiceNow Update Set to v2.9.3 with Instructions for On-Call - #40691
Merged
Merged
Conversation
Add Datadog-Snow_Update_Set_v2.9.3.xml and point the ITOM/ITSM setup guide and the Incident Management ServiceNow page at it. Add a Configure Datadog On-Call section to the ITOM/ITSM setup guide covering the On-Call ServiceNow connection, routing rules, and creating an On-Call page from a ServiceNow business rule. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Preview links (active after the
|
Contributor
Author
|
/review |
Contributor
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
Reviewed the new Configure Datadog On-Call section and the Update Set version bump (v2.8.0 → v2.9.3). The content is clear and the routing_rules link target exists. A few small suggestions on consistency with the rest of the page.
Reviewed d09706574f0bf4b413a75d5789b521cff0d745d2 — workflow run
Move the business rule instructions into Additional configuration options, rephrase the section intro, drop the inline anchor link, and add a language identifier to the code block. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add a table describing the target type, target identifier, and urgency arguments accepted by the PublishOnCallPage script include, along with the page fields derived from the ServiceNow record. Move the version requirement to a note on the Configure Datadog On-Call section. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mathispesch
reviewed
Oct 19, 2026
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
yfangechiu
marked this pull request as ready for review
October 20, 2026 15:21
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
apokellypse
approved these changes
Oct 20, 2026
drichards-87
requested changes
Oct 20, 2026
drichards-87
left a comment
Collaborator
There was a problem hiding this comment.
Left some feedback from Docs.
|
|
||
| **Note**: The integration with Datadog On-Call requires ITOM/ITSM integration version 2.9.3 or newer. | ||
|
|
||
| 1. In Datadog, go to **Incident Response** > **On-Call** > **Settings**. On the left side, select **Integrations**. |
Collaborator
There was a problem hiding this comment.
Suggested change
| 1. In Datadog, go to **Incident Response** > **On-Call** > **Settings**. On the left side, select **Integrations**. | |
| 1. In Datadog, go to **Incident Response** > **On-Call** > **Settings** and select **Integrations**. |
| **Note**: The integration with Datadog On-Call requires ITOM/ITSM integration version 2.9.3 or newer. | ||
|
|
||
| 1. In Datadog, go to **Incident Response** > **On-Call** > **Settings**. On the left side, select **Integrations**. | ||
| 1. Click **ServiceNow**, then click **Add Connection** and configure the settings for the connection with your instance. |
Collaborator
There was a problem hiding this comment.
Suggested change
| 1. Click **ServiceNow**, then click **Add Connection** and configure the settings for the connection with your instance. | |
| 1. Click **ServiceNow**, then click **Add Connection** and configure the connection to your ServiceNow instance. |
|
|
||
| 1. In Datadog, go to **Incident Response** > **On-Call** > **Settings**. On the left side, select **Integrations**. | ||
| 1. Click **ServiceNow**, then click **Add Connection** and configure the settings for the connection with your instance. | ||
| 1. Click a [routing rule][13] for a team, and add a rule that creates a ServiceNow incident when an On-Call page triggers. |
Collaborator
There was a problem hiding this comment.
Suggested change
| 1. Click a [routing rule][13] for a team, and add a rule that creates a ServiceNow incident when an On-Call page triggers. | |
| 1. Open a team's [routing rules][13] and add a rule that creates a ServiceNow incident when an On-Call Page triggers. |
| 1. Click a [routing rule][13] for a team, and add a rule that creates a ServiceNow incident when an On-Call page triggers. | ||
| 1. (Optional) To create a Datadog On-Call Page from ServiceNow, see [Create a Datadog On-Call Page from ServiceNow](#create-on-call-page). | ||
|
|
||
| ## Sync data bidirectionally between ServiceNow and Datadog Work/Incident Management and On-Call {#sync-bidirectionally} |
Collaborator
There was a problem hiding this comment.
Suggested change
| ## Sync data bidirectionally between ServiceNow and Datadog Work/Incident Management and On-Call {#sync-bidirectionally} | |
| ## Sync data bidirectionally between ServiceNow and Datadog {#sync-bidirectionally} |
| {{% /collapse-content %}} | ||
|
|
||
| {{% collapse-content title="Create a Datadog On-Call Page from ServiceNow" level="h3" expanded=false id="create-on-call-page" %}} | ||
| To create a Datadog On-Call Page from a ServiceNow record, add a new business rule in ServiceNow that calls the `PublishOnCallPage` script include. The script include uses the credentials from the **Configuration** record you create in [Sync data bidirectionally](#sync-bidirectionally), so complete that section first. |
Collaborator
There was a problem hiding this comment.
Suggested change
| To create a Datadog On-Call Page from a ServiceNow record, add a new business rule in ServiceNow that calls the `PublishOnCallPage` script include. The script include uses the credentials from the **Configuration** record you create in [Sync data bidirectionally](#sync-bidirectionally), so complete that section first. | |
| To create a Datadog On-Call Page from a ServiceNow record, add a business rule in ServiceNow that calls the `PublishOnCallPage` script include. | |
| Before you start, complete [Sync data bidirectionally](#sync-bidirectionally). The script include uses the credentials from the **Configuration** record you create in that section. |
|
|
||
| | Argument | Required | Description | | ||
| | -------- | -------- | ----------- | | ||
| | Target type | Yes | The kind of target to page: `team_handle`, `team_id`, or `user_id`. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | Target type | Yes | The kind of target to page: `team_handle`, `team_id`, or `user_id`. | | |
| | Target type | Yes | The type of target to page: `team_handle`, `team_id`, or `user_id`. | |
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
drichards-87
approved these changes
Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Datadog-Snow_Update_Set_v2.9.3.xml and point the ITOM/ITSM setup guide and the Incident Management ServiceNow page at it.
Add a Configure Datadog On-Call section to the ITOM/ITSM setup guide covering the On-Call ServiceNow connection, routing rules, and creating an On-Call page from a ServiceNow business rule.
What does this PR do? What is the motivation?
Merge readiness
AI assistance
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.Additional notes