Add agentic onboarding setup to the Azure Container Apps page [SVLS-9614] - #38746
Conversation
…page Replace the separate in-container and sidecar per-language pages with one filterable Cdocs page driven by instrumentation_method and prog_lang content filters. Extract shared serverless-init content into Markdoc partials, add the instrumentation_method trait and serverless option groups, and remove the now orphaned _index translations. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…e nav The per-method pages are consolidated into the single Azure Container Apps Cdocs page, so the child nav items are no longer needed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The ACA instrumentation docs were consolidated from ~16 separate pages (7 runtimes x 2 methods, plus method indexes) into a single Cdocs page driven by runtime + instrumentation-method filters. On one page, all variants "lie flat" in the plaintext/.md version that AI agents (and the serverless llms.txt) consume, so this adds structure back: - Add a heading to each of the 14 content-filter variants (for example "### In-Container: Ruby") so the page exposes stable per-variant anchors (#in-container-ruby, mirroring the former per-variant URLs) and clear section delimiters in the flat plaintext. Headings live inside the filter blocks, so the table of contents stays trait-aware for human readers (verified against the cdocs headings/TOC behavior). - Add `description` frontmatter to improve the serverless llms.txt entry and answer-engine optimization. - Rename the comparison section title to "In-Container vs. Sidecar". Verified with `make build-cdocs` (compiles cleanly; headings render as anchored <h3> inside the filter blocks). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bring the ACA Cdocs migration up to date with master (was 728 commits behind). Conflict resolutions: - content/en/serverless/azure_container_apps/sidecar/nodejs.md: kept deleted. The migration consolidates all sidecar/runtime pages into the single Cdocs page; master's only change to it (#38081, GCP->Azure reference fixes) is already reflected in the consolidated page's partials. - content/.gitignore: union of both sides (kept the ACA _index.md ignore plus master's new cpp / observability_pipelines / session_replay entries). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add DD_AZURE_SUBSCRIPTION_ID and DD_AZURE_RESOURCE_GROUP to the sidecar serverless-init env vars table to match the in-container table and the current published documentation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a prerequisite note to set up the Azure Integration before instrumentation, matching the current published documentation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a sentence after the prerequisite explaining that the setup instruments the application with serverless-init to enable tracing, enhanced metrics, custom metrics, and direct log collection. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Note that enhanced metrics use the azure.app_containerapps.enhanced.* namespace, linking to the Azure Container Apps integration metrics section, matching the current published documentation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a "Set up with agentic onboarding" section (AI Setup CLI and MCP server tabs) mirroring the Google Cloud Run pages, rename the manual "Setup" heading to "Manual instrumentation", and link the MCP serverless_onboarding tool under further reading. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Preview links (active after the
|
|
/review |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
Nice addition. A few small doc-quality items on the new agentic onboarding section:
- The MCP server link on line 81 uses an absolute
docs.datadoghq.comURL; internal docs links should be relative. - The MCP-server tab body on line 81 repeats verbatim ("set up monitoring for your Azure Container Apps with AI assistance") the intro paragraph two lines above.
- The two bullets introducing the paths (lines 64–65) aren't parallel in structure — one is a noun-phrase description, the other is imperative.
- Minor: "Datadog MCP Server" is the product proper noun and is capitalized elsewhere in the doc set (see
content/en/agentic_onboarding/setup.md); line 81 spells it "MCP server".
Reviewed 91e9ea887dc769d9ec58558b8d77a1364a8097c2 — workflow run
There was a problem hiding this comment.
hi @rohanagarwaldd thanks for your PR! just a minor feedback to fix the link, as our docs use relative linking.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
There was a problem hiding this comment.
what if we just had a third switcher here: for agent or not? would that work or would that break things? we could even make it a toggle or something like "AI"
There was a problem hiding this comment.
instead of a third switcher, what do you think about adding a short callout above "Manual Instrumentation" like "Prefer AI-assisted setup? Use the AI Setup CLI or MCP server" and link it to the agentic onboarding doc (https://docs.datadoghq.com/agentic_onboarding/setup/). i'm thinking that the agentic flow is a different entry point, not an instrumentation method option.
There was a problem hiding this comment.
Fair! I'd also love to be able to just have them copy the link to this docs page that an agent can read through and implement for them -- since thats what the AI setup CLI/Onboarding MCP effectively do.
| ## Setup | ||
| ## Set up with agentic onboarding | ||
|
|
||
| Use [agentic onboarding](/agentic_onboarding/setup) to set up monitoring for your Azure Container Apps with AI assistance. Two complementary paths use the same Datadog account: |
There was a problem hiding this comment.
at this point could we just tell customers to point their agent at these docs? or are they not in a good enough state as is?
…tation Move the Azure Integration prerequisite and serverless-init lead-in to a new Overview section at the top, and place the In-Container vs. Sidecar comparison table directly under the Manual instrumentation heading. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…hooting.mdoc.md Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
…oc.md Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
Narrow the generated-file gitignore from /*/ to /en/ so it only ignores the compiled English _index.md, and restore the Spanish, Japanese, and Korean _index.md pages that the broad pattern had swept into deletion. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Updated the overview section to clarify the features of Azure Container Apps and the setup process for Datadog monitoring.
…-docs-improvements
Added prerequisite note for Azure Integration setup.
There was a problem hiding this comment.
not sure how visible this level of detail is and this is also minor but "single container" could be misleading because it implies theres just one container when that may not be the case. i think "bundled with app" would be better.
There was a problem hiding this comment.
This isn't visible, but agreed good callout
Added instructions for agentic onboarding after the prerequisite setup for Azure Integration.
rtrieu
left a comment
rtrieu
left a comment
There was a problem hiding this comment.
approving with one comment about the cdocs option group (selector)
There was a problem hiding this comment.
instead of a third switcher, what do you think about adding a short callout above "Manual Instrumentation" like "Prefer AI-assisted setup? Use the AI Setup CLI or MCP server" and link it to the agentic onboarding doc (https://docs.datadoghq.com/agentic_onboarding/setup/). i'm thinking that the agentic flow is a different entry point, not an instrumentation method option.
Convert the inline agentic onboarding link to a reference-style link per docs convention, and renumber the MCP Server reference to [2] so the two document-wide reference labels don't collide. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rtrieu This is something we can consider. I do agree the current layout can be improved, @ava-silver is taking a look at how we can better display the content. For now, I merged this PR as we need to align with our launch but will keep that in mind for a future PR. |
rohanagarwaldd
changed the title
4 participants
What does this PR do? What is the motivation?
Adds a Set up with agentic onboarding section to the Azure Container Apps page, mirroring the Google Cloud Run pages. The new section presents two setup paths in tabs:
npx @datadog/ai-setup-cli --product serverless --serverless-compute-type=azure-container-appsserverless_onboardingtoolIt also renames the manual Setup heading to Manual instrumentation (matching the Cloud Run pages) and adds the MCP
serverless_onboardingtool to further reading.Merge instructions
Stacked on top of #38440 (the ACA Cdocs migration); the base branch is
rohanagarwal/aca-cdocs-migration. Merge #38440 first, then this PR retargets to the main branch.Merge readiness: