AI Agent Orchestration Platform · View 25 of 32 · 5 · Operations
Decisions
- OpenTelemetry GenAI semantic conventions are the emission contract, so traces are portable off Azure Monitor if that ever matters
- Execution id, workflow id, agent id and correlation id are on every signal, so one identifier joins a trace to its cost and its guardrail decisions
- Prompt and response bodies are captured under privacy policy and stored separately from the trace, referenced by id
What is exposed
- Real-time execution traces, execution graphs, agent timelines, failure analysis and cost breakdowns
- Parent and child span relationships across agent, model, tool and guardrail calls
- Retries, state transitions and guardrail decisions are first-class spans, not log lines
Risks
- Telemetry volume is a genuine cost line; sampling is head-based for successful runs and always-on for failed and escalated ones
- A trace containing prompt text is sensitive; the deep link is authorised separately from the trace itself