Document Multi-View and Operation AI Investigations (preview)

[qsellem]

What does this PR do? What is the motivation?

Documents two new AI Investigation entry points, both in Preview, ahead of the GA of Single-View AI Investigation:

• Multi-View AI Investigation — agentic root-cause analysis on the Optimization page at the (view × vital) granularity. Supports Loading Time, LCP, FCP, and INP; CLS is explicitly called out as not currently supported.
• Operation AI Investigation — agentic root-cause analysis on a single operation in Operations Monitoring. Covers both success rate (Errors / Timeouts / Abandoned) and latency (Performance regression), with findings grouped by frontend / backend / network root causes.

Each new page includes a "Join the Preview!" callout linking to a placeholder product-preview URL. The AI Investigations _index.md lists both new sections, and operations_monitoring.md cross-links to the new Operation AI Investigation page.

Merge instructions

Merge readiness:

• Ready for merge

Additional notes

• Preview URLs are placeholders (rum-multi-view-ai-investigation and rum-operation-ai-investigation) and need to be replaced with the real product-preview slugs before merge.
• Screenshots will be added before GA.

[github-actions]

Preview links (active after the build_preview check completes)

New or renamed files

• https://docs-staging.datadoghq.com/quentin.sellem/rum_agentic_investigations_part2/real_user_monitoring/ai_investigations/multi_view_ai_investigation
• https://docs-staging.datadoghq.com/quentin.sellem/rum_agentic_investigations_part2/real_user_monitoring/ai_investigations/operation_ai_investigation

Modified Files

• https://docs-staging.datadoghq.com/quentin.sellem/rum_agentic_investigations_part2/real_user_monitoring/ai_investigations/
• https://docs-staging.datadoghq.com/quentin.sellem/rum_agentic_investigations_part2/real_user_monitoring/ai_investigations/single_view_ai_investigation
• https://docs-staging.datadoghq.com/quentin.sellem/rum_agentic_investigations_part2/real_user_monitoring/operations_monitoring

[datadog-datadog-prod-us1]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/documentation | build_preview     

🔄 Retry job. This looks flaky and may succeed on retry.

Failed to access repository due to server busy, returning HTTP error 503.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: b52c2f1 | Docs | Datadog PR Page | Give us feedback!}

[rtrieu]

hi @qsellem thanks for this PR! left suggestions around formatting and consistency. once you finish reviewing these suggestions, i'd like to make a commit to make sure the headers and terminology are consistent across all the pages, including single view investigation.

[rtrieu]

made a commit with the following changes:

• updated “Core Web Vital” in the overview to a broader term “performance vital” since we also look at Loading Time
• reordered the sections so that they are aligned across all 3 pages:
  • Launch
  • Data analyzed
  • Read results
• added a “Take Action” section to Single-View to match the other 2 pages

quentin to add preview form URLs