[FEATURE] Support multiple OTEL endpoints simultaneously for telemetry export
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When an organization has configured OpenTelemetry (OTEL) export via managed settings, individual users cannot simultaneously send telemetry to a personal endpoint for local monitoring, debugging, or compliance purposes. Managed settings have high precedence and cannot be overridden, making it impossible to duplicate telemetry to multiple destinations.
Proposed Solution
Allow users to configure additional OTEL exporters in their personal ~/.claude/settings.json that work alongside (not instead of) the managed OTEL configuration. Options:
- Support comma-separated multiple OTLP endpoints in the same exporter configuration
- Allow personal settings to add supplementary exporters while respecting the managed endpoint
- Provide a way to configure multiple OTEL exporter instances with different endpoints
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
A developer in an organization with centralized OTEL monitoring wants to:
- Send telemetry to the org's managed OTEL endpoint (required by policy)
- Also send the same telemetry to a personal observability platform (e.g., Datadog, New Relic, or local Grafana instance) for personal debugging and performance analysis
Currently, this is not possible because the managed endpoint configuration prevents any personal OTEL configuration from taking effect.
Additional Context
- Related documentation: Monitoring usage
- The OTEL exporter already supports multiple exporters (e.g., OTEL_METRICS_EXPORTER=console,otlp), but there's no documented way to configure multiple OTLP endpoints with different targets
- This would be useful for organizations that want both centralized compliance monitoring and individual developer observability