Skip to content

Document How-to: create alerts on Agent Builder trace/usage data #7173

Description

@charlotte-hoblik

Parent: elastic/docs-content-internal#1252

Agent Builder collects agent execution traces as OpenTelemetry data in the user's own {es} cluster (data stream traces-agent_builder.otel-). Because these traces capture token usage, error status, span durations, and tool invocations, users can build Kibana alert rules directly on the trace data. There is no dedicated alerting UI. This is an explicitly doc-first deliverable: the team surfaces the data in dashboards first (#7170), then enables alerting through documentation.

Lifecycle: GA in 9.5 (Stack and Serverless). Trace collection and the overview dashboard are GA in 9.5 (gate agentBuilder:experimentalFeatures removed in kibana#276174; traces GA signed off in search-team#15134). Alerting rides on GA trace data plus existing Kibana alerting, which is already GA. agentBuilder:tracing:enabled (default true) is the sole control. (Previously listed as Technical Preview behind the experimental flag; that is stale.)

Content type: How-to. New page in the Agent Builder section next to collect-traces.md (#7171) and agent-traces-dashboard.md (#7170).

Dependencies:

Depends on trace collection docs (#7171, draft PR #7322).
Reuses the span/attribute reference from the dashboard page (#7170, draft PR #7337).

Depends on: trace collection (elastic/search-team#14684) being documented first. Contacts: @meghanmurphy1.

Metadata

Metadata

Labels

Team:DeveloperIssues owned by the Developer Docs TeamdocumentationImprovements or additions to documentation

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions