docs: add PagerDuty to the Pro Integrations tool reference#15210
Open
devGregA wants to merge 1 commit into
Open
docs: add PagerDuty to the Pro Integrations tool reference#15210devGregA wants to merge 1 commit into
devGregA wants to merge 1 commit into
Conversation
Covers instance setup (REST API key, From user email, regional API base URL), the service ID mapping identifier, the urgency vs account-priority severity mapping modes, status mappings, and the PagerDuty-specific caveats (resolved is final; title/body cannot be edited after creation). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Maffooch
force-pushed
the
sc-13642_pagerduty_docs
branch
from
0eda6ef to
9cc6efe
Compare
Maffooch
approved these changes
Jul 10, 2026
paulOsinski
approved these changes
Jul 10, 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
3 participants
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.
Summary
Adds PagerDuty to the Pro Integrations documentation:
integrations.md: lists PagerDuty among the supported integrations.integrations_toolreference.md: new PagerDuty section covering instance setup (REST API key from Integrations > API Access Keys, From user email required by PagerDuty for incident writes, and the EU regional API base URL), the Service ID mapping identifier, severity mapping to incident Urgency by default or to account Priority names when the field name is set toPriority, status mappings (triggered / acknowledged / resolved), and the PagerDuty-specific caveats (resolved is final; incident title/body cannot be edited after creation, so updates sync status/urgency/priority only).Documents the feature shipping via DefectDojo-Inc/dojo-pro#1820 and DefectDojo-Inc/go-integrators#177 (Shortcut sc-13642).
🤖 Generated with Claude Code