Put Copilot OpenTelemetry Export Behind an Isolated Collector

Short summary

GitHub's enterprise-managed OpenTelemetry export for Copilot activity requires an isolated collector architecture, not direct-to-backend piping. The article recommends a dedicated collector pool with write-only credentials, a strict field budget that drops raw prompts and file paths by default, bounded retry queues, and a rollback switch in enterprise management. It includes illustrative OTel processor configs and a testing checklist for cardinality bursts, forbidden-field injection, and backend outages.

• •Route Copilot telemetry through a dedicated OTel Collector pool, not directly to production backends
• •Drop raw prompts, file paths, and user emails by default; use scoped pseudonymous identity
• •Bounded retries, visible queue growth, and enterprise-managed rollback switch are required for operability

Generated with AI, which can make mistakes.