and communication - Modality agnostic (Text, Audio, Video) - Enterprise focus - security, long running, built on standards - Complements MCP, it doesn’t compete Agent to Agent (A2A) FOLLOW US CLOUDNATIVEDAYSITALY.ORG
operations • Enable your orchestrations to be resilient to agent and infrastructure failure • You have an out-of-the-box audit trail to trace back why an agent made or not a given decision or why it called a specific tool
Kubernetes … Infrastructure The OpenTelemetry Collector Receive Process Export Time-series database Log database Trace database … Generate and Emit transmit Collect, Convert, Process, Route, Export transmit Store & Analyze Collection of Telemetry is standardized Vendor space “The last observability agent you will ever install” … and many more.
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
• We have GenAI Semantic Conventions which are starting to align • We need more conventions, from workflows to skills and everything in between • Telemetry is becoming more important, as it can provide context for our agents to learn • So….
evaluating OpenTelemetry support • Inspired by the CNCF Platform Engineering maturity model • Descriptive, not prescriptive • Focused on evolution, not scoring Github Issue: https://github.com/open-telemetry/community/issues/3247 Project Proposal: https://github.com/open-telemetry/community/pull/3435