Draft
Conversation
Contributor
…6, and blocking mode
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 does this PR do? What is the motivation?
Refactors the AI Guard documentation from a single onboarding page into a structured multi-page layout.
Commit-by-commit breakdown
Extract security signals into dedicated page — Moves the security signals section from the onboarding page to a new
signals.mdpage, with a summary and link left in onboarding.Extract setup instructions into dedicated page — Moves the full setup steps (prerequisites, API keys, Agent, retention filter, policies, access control) from the onboarding page to a new
setup/section.Create setup subpages for integrations, SDK, and HTTP API — Creates four subpages under setup: automatic integrations, manual integrations, SDK, and HTTP API. Moves SDK and REST API content from onboarding into their respective pages.
Remove API and SDK sections from onboarding page — Cleans up the onboarding page after content was moved to subpages.
Add Datadog Agent setup section to integrations and SDK pages — Adds the Agent setup prerequisite to automatic integrations, manual integrations, and SDK pages.
Move tracer library install section from setup index to SDK page — Moves the tracer install instructions (Python, JS, Java, Ruby) to the SDK page where they belong.
Replace Agent setup step with instrumentation options overview — Replaces step 3 in the setup index with an overview of all instrumentation options (SDK, automatic integrations, manual integrations, HTTP API) with links to each subpage.
Reorder onboarding sections and trim HTTP API page — Reorders sections in onboarding and removes env vars table and request message format from the HTTP API page.
Update automatic integrations with env vars, AI SDK v6, and blocking mode — Updates automatic integrations page with the correct AI SDK v6 version, required environment variables, and blocking mode documentation.
Update SDK docs with tags, sds, and accurate method signatures — Updates Python, JavaScript, and Java SDK docs with
tagsandsdsreturn fields, fixes parameter descriptions, and adds JavaMessage.tool()example.Add SDS category and rule tag attributes to detection rules — Adds
@ai_guard.sds.categoriesand@ai_guard.sds.rule_tagsto the detection rules attribute table.Add warning that HTTP API requests don't appear in Datadog UI — Adds a warning banner explaining that HTTP API evaluations don't send traces to Datadog.
Merge instructions
Merge readiness: