Skip to content

Conversation

@codefromthecrypt
Copy link
Contributor

Define how agents export telemetry (logs, metrics, traces) to clients without tunneling over the ACP transport.

  • Clients run a local OTLP receiver and inject OTEL_EXPORTER_* env vars when launching agents
  • Keeps telemetry out-of-band to avoid head-of-line blocking on stdio
  • Agents use standard OpenTelemetry SDKs with auto-configuration
  • No credential sharing: client proxies telemetry to backends with its own credentials
  • Complements meta-propagation RFD (trace context correlation)

Implementation proposes a new docs/protocol/observability.mdx covering both client and agent author guidance.

extracted from #295 (comment)

Copy link
Member

@benbrandt benbrandt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I think this makes sense and is largely a guide with recommendations on how to use (can also revisit with the registry later)

Thanks!

@benbrandt benbrandt force-pushed the rfd/agent-telemetry-export branch from b95e2c8 to dc62527 Compare December 11, 2025 13:29
@benbrandt benbrandt enabled auto-merge (squash) December 11, 2025 13:30
@benbrandt benbrandt disabled auto-merge December 11, 2025 13:31
@benbrandt benbrandt enabled auto-merge (squash) December 11, 2025 13:32
@benbrandt benbrandt merged commit 7b332e1 into agentclientprotocol:main Dec 11, 2025
1 check passed
@codefromthecrypt codefromthecrypt deleted the rfd/agent-telemetry-export branch December 12, 2025 08:03
@codefromthecrypt
Copy link
Contributor Author

Thanks I will report back with an impl!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants