--- title: Client telemetry user attribution and configurable capture description: GitHub Copilot now supports a telemetry.capture.identity setting that lets enterprise administrators attribute Copilot activity to a specific user via OTel... canonical: https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Client telemetry user attribution and configurable capture | daily.dev og:description: GitHub Copilot now supports a telemetry.capture.identity setting that lets enterprise administrators attribute Copilot activity to a specific user via OTel... og:url: https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3 og:image: https://api.daily.dev/og/posts/wlzlxKLp3.png og:image:alt: Client telemetry user attribution and configurable capture og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Client telemetry user attribution and configurable capture **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 2 min read · 0 upvotes · 0 comments ## Summary GitHub Copilot now supports a telemetry.capture.identity setting that lets enterprise administrators attribute Copilot activity to a specific user via OTel attributes (user.name, process.user.name, host.name), without collecting prompt or response content. This is off by default and separate from the existing pseudonymous identifier. Admins can also independently toggle five other capture classes (prompts, responses, toolArguments, toolOutput, policyDetail), all off by default, with managed settings taking precedence over local config. The legacy captureContent setting remains as shorthand for content classes but never enables identity capture. Fine-grained controls apply to Copilot CLI, the Copilot app, and VS Code sessions using Agent Host. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What does the telemetry.capture.identity setting do in GitHub Copilot? It lets enterprise administrators attribute Copilot activity to a specific user by adding three attributes to OpenTelemetry data: user.name (the authenticated Copilot account, currently the GitHub login), process.user.name (the local OS account), and host.name (the local machine name). It is off by default and separate from the existing pseudonymous user identifier. _Admins rolling out Copilot governance can track settings like this via daily.dev to stay ahead of compliance requirements._ ### What telemetry capture classes can GitHub Copilot enterprise admins control independently? Five classes: prompts (user, system, and developer prompts plus input context), responses (assistant responses and reasoning content), toolArguments (raw tool arguments, commands, schemas, and identifiers for tools, MCP servers, plugins, hooks), toolOutput (tool results and execution errors), and policyDetail (raw policy details like sandbox filesystem paths). All are off by default and managed values override local settings. _Teams designing audit policies for AI coding tools can follow granular capture controls like these on daily.dev._ ### Does enabling captureContent in GitHub Copilot also enable identity capture? No. The legacy captureContent setting remains available as shorthand for enabling the five content capture classes (prompts, responses, toolArguments, toolOutput, policyDetail), but it never enables identity capture; telemetry.capture.identity must be set separately and explicitly. _Anyone configuring Copilot telemetry for compliance can watch for nuances like this on daily.dev before shipping a policy._ ## Similar posts on daily.dev - [Enterprise-managed OpenTelemetry export for VS Code and CLI](https://daily.dev/posts/enterprise-managed-opentelemetry-export-for-vs-code-and-cli-91hzfrboq) · GitHub Changelog · 0 upvotes · 0 comments - [OpenTelemetry in the GitHub Copilot app](https://daily.dev/posts/opentelemetry-in-the-github-copilot-app-5hmkxo5ng) · GitHub Changelog · 1 upvotes · 0 comments - [Monitoring GitHub Copilot usage with the Aspire Dashboard](https://daily.dev/posts/monitoring-github-copilot-usage-with-the-aspire-dashboard-0cezslpyu) · The Art of Simplicity · 0 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#vscode](https://daily.dev/tags/vscode), [#opentelemetry](https://daily.dev/tags/opentelemetry) [View this post on daily.dev](https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Client telemetry user attribution and configurable capture","url":"https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3"},"datePublished":"2026-10-13T02:57:40.589Z","dateModified":"2026-10-13T02:58:02.058Z","description":"GitHub Copilot now supports a telemetry.capture.identity setting that lets enterprise administrators attribute Copilot activity to a specific user via OTel...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/130b3bca59caa9a1837c28072eef0242?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/130b3bca59caa9a1837c28072eef0242?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,vscode,opentelemetry","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Client telemetry user attribution and configurable capture"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/client-telemetry-user-attribution-and-configurable-capture-wlzlxklp3#faq","mainEntity":[{"@type":"Question","name":"What does the telemetry.capture.identity setting do in GitHub Copilot?","acceptedAnswer":{"@type":"Answer","text":"It lets enterprise administrators attribute Copilot activity to a specific user by adding three attributes to OpenTelemetry data: user.name (the authenticated Copilot account, currently the GitHub login), process.user.name (the local OS account), and host.name (the local machine name). It is off by default and separate from the existing pseudonymous user identifier. Admins rolling out Copilot governance can track settings like this via daily.dev to stay ahead of compliance requirements."}},{"@type":"Question","name":"What telemetry capture classes can GitHub Copilot enterprise admins control independently?","acceptedAnswer":{"@type":"Answer","text":"Five classes: prompts (user, system, and developer prompts plus input context), responses (assistant responses and reasoning content), toolArguments (raw tool arguments, commands, schemas, and identifiers for tools, MCP servers, plugins, hooks), toolOutput (tool results and execution errors), and policyDetail (raw policy details like sandbox filesystem paths). All are off by default and managed values override local settings. Teams designing audit policies for AI coding tools can follow granular capture controls like these on daily.dev."}},{"@type":"Question","name":"Does enabling captureContent in GitHub Copilot also enable identity capture?","acceptedAnswer":{"@type":"Answer","text":"No. The legacy captureContent setting remains available as shorthand for enabling the five content capture classes (prompts, responses, toolArguments, toolOutput, policyDetail), but it never enables identity capture; telemetry.capture.identity must be set separately and explicitly. Anyone configuring Copilot telemetry for compliance can watch for nuances like this on daily.dev before shipping a policy."}}]} ```