telemetry-instrumentation Skill
Instrumentation patterns for telemetry in the vscode-documentdb extension. Use when adding telemetry to a feature, enriching existing telemetry with properties or measurements, linking related events with correlation IDs, instrumenting commands or tree views, suppressing noisy events, or deciding what data points to ca Published by microsoft in vscode-documentdb.
What is telemetry-instrumentation Skill?
Instrumentation patterns for telemetry in the vscode-documentdb extension. Use when adding telemetry to a feature, enriching existing telemetry with properties or measurements, linking related events with correlation IDs, instrumenting commands or tree views, suppressing noisy events, or deciding what data points to ca Published by microsoft in vscode-documentdb. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use telemetry-instrumentation Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-documentdb
- Skill file: .github/skills/telemetry-instrumentation/SKILL.md
What it does
Instrumentation patterns for telemetry in the vscode-documentdb extension. Use when adding telemetry to a feature, enriching existing telemetry with properties or measurements, linking related events with correlation IDs, instrumenting commands or tree views, suppressing noisy events, or deciding what data points to ca
Skill instructions
Telemetry Instrumentation How to instrument code in vscode-documentdb to produce actionable telemetry. What the Framework Gives You for Free The @microsoft/vscode-azext-utils library automatically captures these — never add them manually: | Auto-captured | Details | | ----------------------- | ------------------------------------------------------------------ | | Duration | measurements.duration — wall-clock ms from callback start to end | | Result | properties.result — "Succeeded", "Failed", or "Canceled" | | Error info | properties.error (name), properties.errorMessage (message) | | Cancel detection | UserCancelledError sets result to "Canceled" automatically | | Machine/session IDs | VSCodeMachineId, VSCodeSessionId — always present | | Extension metadata | Extension name, version, VS Code version | Do not re-measure duration, set result, or catch errors just for telemetry — the wrapper handles it. Core API callWithTelemetryAndErrorHandling(eventId, callback) The primary wrapper. Cr
Explore related resources
Frequently asked questions
What is telemetry-instrumentation?
telemetry-instrumentation is a open-source AI agent skill with Copy skill directory. Instrumentation patterns for telemetry in the vscode-documentdb extension.
Who is telemetry-instrumentation best for?
telemetry-instrumentation is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install telemetry-instrumentation?
Install or run telemetry-instrumentation using Copy skill directory. Check telemetry-instrumentation for the latest setup command.
Is telemetry-instrumentation actively maintained?
telemetry-instrumentation may need a closer maintenance check before production use.
Auto-fetched from GitHub.
