docs(integrations): Opsgenie integrator reference#15277
Draft
devGregA wants to merge 1 commit into
Draft
Conversation
Add the Opsgenie section to the Pro integrations tool reference (instance setup with GenieKey API integration keys and regional / JSM Operations base URLs, optional Team responder identifier, P1-P5 priority mapping, open/acknowledged/closed status mapping with the closed-is-final and alias-dedupe notes) and list Opsgenie on the integrations overview page. Story: sc-13748 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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
Documents the new Opsgenie Pro integrator (story sc-13748):
open/acknowledged/closed, with the closed-is-final caveat, the content-edits-do-sync note (unlike PagerDuty), and the alias-based de-duplication behavior.Companion PRs
🤖 Generated with Claude Code