and communication - Enterprise focus - security, long running, built on standards - Modality agnostic (Text, Audio, Video) - Complements MCP, it doesn’t compete Agent to Agent (A2A)
bot assist to create the order ◦ Level 2 - GenAI Augmented -> agents driving the operations, humans approve ▪ Level 3 - Spec-Centric -> analyze the order and validate what is delivered • Level 4 - Selective Autonomy -> selecting drinks is auto approved ◦ Level 5 - Full Autonomy -> human needed when oven breaks BLOG https://www.salaboy.com/2026/06/08/reacting-to-ai/
But, • many spans represent infrastructure • some represent retries or polling (it can create a lot of noise) • some represent framework calls (chatty MCP / A2A) Goal: meaningful spans, not just more spans
scripts • external tools • subprocesses These components: • are not instrumented • do not propagate trace context • break traces Java Agent TRACEPARENT env Shell script curl with trace header Service span
the CookingAgent cooked 10K pizzas - 99% ✅ - 1 % failed - Can we accept to refund 100 pizzas if things go wrong in exchange to let our Agent unsupervised? Moving to Level 4
Otel GenAI Semantic Conventions are a good step forward 03 We need more conventions for workflows & skills 04 Telemetry is critical to understand and validate agents