Add step-by-step usage guides for the bundled PagerDuty and Datadog extensions - #10
Merged
Merged
Conversation
…xtensions Two new pages under Guides walk through connecting and using each built-in connector: the PagerDuty OAuth browser flow plus its three read-only incident tools (accepted incident URL/ID/number forms, tool knobs, troubleshooting), and the Datadog API-key form (where to get the two keys, site selection, log-search query/time-range/pagination inputs, troubleshooting including the wrong-site-looks-like-wrong-keys pitfall). Cross-linked from Using Extensions and the Extensions Overview. 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.
What
Two new hands-on pages under Guides, documenting how to use the two first-party bundled extensions:
docs/guides/pagerduty-extension.md— the OAuth browser connect flow (including the transient localhost redirect note), the three read-only incident tools with a summary table, accepted incident reference forms (URL / ID / number), example prompts, the user-tunable knobs (log-entry inclusion/limit, past-incident count), troubleshooting (not-connected, reconnect, 403 permissions, unparseable reference), and disconnecting.docs/guides/datadog-extension.md— where to create the API + application keys (and thelogs_read_datapermission), a login-URL → site mapping table, the inline connect form, example prompts, a prompt-phrase → tool-input mapping table (query syntax, time ranges, limit, sort, indexes, cursor pagination), returned-event fields, troubleshooting (including the wrong-site-looks-like-invalid-keys pitfall), and key rotation.Both pages reuse the existing card screenshots and link onward to the Incident Analysis walkthrough and the corresponding building-extensions pages.
Cross-links
Verification
npm run buildpasses (link checking + MDX).server.cjssources in the app repo.