copilot-otel-metrics
Installation
SKILL.md
Copilot OpenTelemetry Metrics
Goal
Take the user from "I want Copilot telemetry" to telemetry they can query. Do the work for them where doing it is safe and reversible, and walk them through it where it is not.
Done means export is enabled in the settings file that actually resolves, a backend is receiving data, a dashboard exists for that backend, and the user has confirmed data landed by querying the store rather than by trusting an HTTP 200.
Modes
Modes are independent. A user may run one, several, or all. Local capture and organization capture are separate journeys, not stages of the same one.
| Mode | Use when the user wants to | Consent gate | Reference |
|---|---|---|---|
local-setup |
Turn on Copilot's OTel export on this machine | Show the exact settings diff and write only after approval | references/local-setup.md |
local-stack |
Get a backend on this machine to receive it | Write the files, then hand over the command; never run it | references/local-stack.md |
org-distribution |
Push OTel settings to a fleet of developers | Nothing is applied; draft the configuration and explain it | references/org-distribution.md |
azure-capture |
Collect a fleet's telemetry into Azure and chart it | Write the templates, then hand over the deploy commands | references/azure-capture.md |