otel-observability

To instrument agents with OpenTelemetry traces and metrics, use the four OTel tools exposed via an MCP server. Each Copilot session gets its own server instance that emits OTLP data to a shared collector for unified observability across parallel domain squads.

The best way to track operation durations in federated squad agents is using the otel_span tool. It measures operation durations while carrying attributes, allowing you to capture detailed performance telemetry across distributed domain sessions and meta-squad contexts.

You set up an observability dashboard for OpenTelemetry data using the integrated Aspire dashboard. The dashboard workflow connects to OTLP endpoints to visualize traces, metrics, and logs, and is launched using provided start-up scripts for immediate real-time telemetry monitoring.

Yes, you can capture human-readable decisions and debugging logs with OpenTelemetry using the otel_log tool. It records decision and debug details directly into your telemetry pipeline, feeding them into the unified Aspire observability dashboard alongside traces and metrics.

Yes, this OpenTelemetry instrumentation works across parallel domain squads. It applies domain-wide instrumentation patterns to federated squad agents, ensuring each session emits OTLP data to a shared collector for consistent observability across all meta-squad contexts.

You need to emit metrics at completion points using OpenTelemetry to track operational counters and gauges. The otel_metric tool records values like resources analyzed or lessons learned, providing quantitative telemetry for your federated squad agents upon step completion.