[Agent Builder] Document trace collection (9.5)

[charlotte-hoblik]

Summary

Documents Agent Builder OpenTelemetry trace collection for 9.5. This is the foundational page for the Agent Builder trace docs cluster (collection, dashboards, alerting).

What's added

• New page: Collect agent traces (collect-traces.md), registered in the nav after Monitor usage and costs. It covers:
  • The two OTel data streams: traces-agent_builder.otel-* (execution spans) and logs-agent_builder.otel-* (opt-in conversation content).
  • Enabling and configuring collection, and the trace privacy settings (GenAI Settings > Agent Builder Traces).
  • Granting read access to trace data.
  • Exporting traces to a remote OTLP endpoint (Stack only).
• permissions.md: new "Read trace data" subsection for the trace index privileges.
• chat.md: new "View traces for a conversation round" section for the trace waterfall button.

Lifecycle

Trace collection is GA in 9.5 (Stack and Serverless). The overview dashboard is GA (elastic/search-team#15134). The built-in traces skill is Technical Preview in 9.5. Remote OTLP export is Stack only, because it is configured in kibana.yml, which serverless does not expose.

Closes

Closes #7171. Part of elastic/docs-content-internal#1252.

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• explore-analyze/ai-features/agent-builder/chat.md
• explore-analyze/ai-features/agent-builder/collect-traces.md
• explore-analyze/ai-features/agent-builder/permissions.md

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 4 warnings, 1 suggestion found

⚠️ Warnings (4): Fix when the suggestion improves clarity or correctness.

File	Line	Rule	Message
explore-analyze/ai-features/agent-builder/collect-traces.md	49	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
explore-analyze/ai-features/agent-builder/collect-traces.md	59	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
explore-analyze/ai-features/agent-builder/collect-traces.md	90	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
explore-analyze/ai-features/agent-builder/permissions.md	109	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.

💡 Suggestions (1): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
explore-analyze/ai-features/agent-builder/chat.md	200	Elastic.Wordiness	Consider using 'these' instead of 'all of these'.

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.