What problem does it solve?
Turning on GitHub Copilot's OpenTelemetry export is error-prone: settings names change between extension builds, prompt content leaks into spans even with content capture disabled, and there is no direct path from VS Code to Azure Monitor. This Skill walks the user from zero to queryable telemetry, handling the settings write, the backend stack, and the dashboard while keeping the user in control of every mutation.
Core Features & Use Cases
- Four independent modes: local-setup (diff-approved settings write), local-stack (digest-pinned Collector plus Grafana LGTM compose stack), org-distribution (fleet settings guidance), and azure-capture (Bicep, Terraform, and CLI templates for Application Insights and Log Analytics).
- Fail-closed telemetry filtering: the bundled Collector configuration drops unknown attributes and scrubs prompt content carriers before storage, with runtime tests proving what the filter reaches.
- Verification-first workflow: helper scripts (verify.py, baseline.py, inspect_metrics.py, validate_dashboard.py) confirm data actually landed in the store rather than trusting exporter response codes.
- Use Case: A platform engineer wants organization-wide Copilot usage metrics. The Skill generates the Azure collector config, infrastructure templates, and a KQL dashboard, explains the shared ingest credential risk, and hands over deploy commands for the operator to run.
Quick Start
Ask the agent to set up Copilot OpenTelemetry metrics locally, and it will propose the settings diff and generate the local Grafana stack for you to start.