GitHub Adds Enterprise OpenTelemetry Export to the Copilot App
Managed settings can now route agent traces into compatible monitoring tools, with prompt and response content excluded unless administrators change capture settings.
Edited by Tyronne Panaino
GitHub added OpenTelemetry configuration to the Copilot app on September 22, allowing enterprise administrators to send agent activity data to compatible monitoring tools through centrally managed settings. The official GitHub changelog says prompt and response content is excluded by default and tells administrators to review content-capture settings before enabling the export.
The release gives platform and engineering teams a shared observability path for Copilot agent sessions. GitHub says the data can show a session's flow, including requests to AI models and the tools an agent uses, so investigators can follow execution step by step in monitoring systems they already operate. The announcement establishes the export feature and its default content boundary; it does not establish a complete audit record or a compliance outcome.
What administrators can configure
The configuration is delivered through enterprise-managed settings. Administrators enable export with the `telemetry` property in `managed-settings.json` and specify the endpoint that will receive the data. GitHub presents centralized configuration as a way to apply the same telemetry settings across teams instead of asking each developer to configure an exporter separately.
For organizations already collecting distributed traces, the practical delta is that Copilot app agent activity can enter the same compatible monitoring environment as other operational signals. A trace can help a team reconstruct how an agent moved through model requests and tool calls, compare steps across sessions, and investigate unexpected behavior with a familiar interface. Those are documented uses of the telemetry; the source does not claim that every local action, external side effect or security-relevant event is captured.
The default content boundary
GitHub explicitly says prompt and response content is excluded by default. That distinction matters because activity metadata and conversation content carry different privacy and security implications. A default exclusion can reduce the amount of sensitive natural-language material sent to a monitoring endpoint, but it does not by itself describe every exported attribute or guarantee that traces contain no confidential metadata.
The release also warns administrators to review content-capture settings before enabling the feature. Teams should therefore treat the receiver, transport, retention policy and access control as part of the deployment rather than assuming the Copilot setting settles those questions. The fetched announcement does not provide retention periods, a field-level schema, endpoint authentication details or an independent privacy assessment.
How this differs from earlier IDE telemetry
AI Signal previously covered OpenTelemetry controls in GitHub's JetBrains plugin. This September release is a separate product event: it concerns the GitHub Copilot app and enterprise-managed export for agent monitoring. The reader purpose is consequently different. The earlier update explained IDE plugin controls, while this one focuses on organization-wide tracing of app sessions and the default boundary around prompt and response capture.
That distinction also limits what can be inferred. Availability in one Copilot surface does not prove identical fields, defaults or behavior in another. Administrators should validate the app's traces against their monitoring and incident-response requirements before treating them as authoritative evidence.
Evidence quality and limits
Internal confidence is medium because the article relies on one official GitHub release note. The source confirms availability, configuration placement, intended monitoring uses and the default exclusion of prompt and response content. It provides no independent completeness test, performance cost, security review, reliability measurement or proof that telemetry prevents unsafe agent behavior.
Status
Confirmed. GitHub documents enterprise-managed OpenTelemetry support in the Copilot app; trace completeness and operational outcomes remain unverified.
Sources
Update note: Last reviewed 2026-09-23. We will revise this post if GitHub changes export defaults, content-capture behavior, configuration scope or availability.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.