Enterprise-managed OpenTelemetry export for VS Code and CLI

Organizations can now mandate where GitHub Copilot sends OpenTelemetry (OTel) data, so telemetry flows to an approved collector without each developer setting OTEL_* environment variables. The configuration is delivered through the telemetry block in enterprise-managed settings and applies to both the Copilot Chat extension in VS Code and the agent host process that powers Copilot CLI.

Administrators can control:

• The OTLP export endpoint and transport protocol (otlp-http or otlp-grpc).
• The OTel service name and resource attributes.
• Exporter headers, such as an authentication token for the collector.
• Whether prompt, response, and tool content is captured, and whether developers can change that.

A managed value always wins, taking precedence over environment variables and user settings. Deliver these settings through any of the supported channels: native MDM (Windows Registry or macOS managed preferences), server-managed settings resolved from the signed-in GitHub account, or a file-based managed-settings.json.

For security, managed exporter headers are applied only to the Copilot Chat extension’s OTLP exporter and are never passed through environment variables, so a value such as an authentication token can’t leak into the tool subprocesses that the agent host spawns.

This builds on enterprise managed settings and joins the growing set of Copilot governance controls available across VS Code and Copilot CLI.

To learn more, see Configure telemetry export with OpenTelemetry and Monitor agent usage with OpenTelemetry.

Join the discussion within GitHub Community.

The post Enterprise-managed OpenTelemetry export for VS Code and CLI appeared first on The GitHub Blog.