appinsights-instrumentation — GitHub Copilot skill
This skill adds telemetry to a web app and sends it to Azure App Insights. Use it when an Azure-hosted app needs better visibility into its health.
npx skills add github/awesome-copilot --skill appinsights-instrumentationWhat appinsights-instrumentation does
The skill identifies the app's language, framework, and hosting setup, then selects an Azure App Insights integration path. It targets ASP.NET Core and Node.js apps hosted in Azure. The hosting environment must be confirmed before setup.
For the App Insights resource, the skill can extend an existing Bicep template or use the Azure CLI command from scripts/appinsights.ps1. It recommends placing the resource in the resource group used by the hosted app. Separate code instructions cover ASP.NET Core, Node.js, and Python.
Install it when your app runs in Azure and you need application telemetry. A local app without Azure is outside this skill's intended use.
What it helps with
- add telemetry to a web app
- create an Azure App Insights resource
- connect App Insights to an ASP.NET Core app
- configure data collection in a Node.js app
- choose between Bicep and Azure CLI setup
Example prompts for the agent
- Add telemetry to this ASP.NET Core app and confirm how it is hosted.
- Set up Azure App Insights for this Node.js app using the suitable resource creation path.
- Inspect the project and connect App Insights with `scripts/appinsights.ps1` if there is no Bicep template.
How to install appinsights-instrumentation
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill appinsights-instrumentation2GitHub CLI
gh skill install github/awesome-copilot appinsights-instrumentation3Manually: put the files in place
.github/skills/appinsights-instrumentation/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill appinsights-instrumentation -a claude-code2Manually: put the files in place
~/.claude/skills/appinsights-instrumentation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/appinsights-instrumentation/
Manually: put the files in place
.agents/skills/appinsights-instrumentation/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/appinsights-instrumentation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/appinsights-instrumentationManually: put the files in place
.devin/skills/appinsights-instrumentation/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about appinsights-instrumentation
How do I install appinsights-instrumentation in GitHub Copilot?
Run npx skills add github/awesome-copilot --skill appinsights-instrumentation, then use .github/skills/appinsights-instrumentation/SKILL.md.
What does appinsights-instrumentation do?
The skill helps connect Azure App Insights to a web app, create the resource, and update application code to send telemetry.
What applications does appinsights-instrumentation support?
The workflow targets ASP.NET Core and Node.js apps hosted in Azure. The skill also includes a separate guide for Python code.
Source text
SKILL.md · MIT
--- name: appinsights-instrumentation description: 'Instrument a webapp to send useful telemetry data to Azure App Insights' --- # AppInsights instrumentation This skill enables sending telemetry data of a webapp to Azure App Insights for better observability of the app's health. ## When to use this skill Use this skill when the user wants to enable telemetry for their webapp. ## Prerequisites The app in the workspace must be one of these kinds - An ASP.NET Core app hosted in Azure - A Node.js app hosted in Azure ## Guidelines ### Collect context information Find out the (programming language, application framework, hosting) tuple of the application the user is trying to add telemetry support in. This determines how the application can be instrumented. Read the source code to make an educated guess. Confirm with the user on anything you don't know. You must always ask the user where the application is hosted (e.g. on a personal computer, in an Azure App Service as code, in an Azure App Service as container, in an Azure Container App, etc.). ### Prefer auto-instrument if possible If the app is a C# ASP.NET Core app hosted in Azure App Service, use [AUTO guide](references/AUTO.md) to help user auto-instrument the app. ### Manually instrument Manually instrument the app by creating the AppInsights resource and update the app's code. #### Create AppInsights resource Use one of the following options that fits the environment. - Add AppInsights to existing Bicep template. See [examples/appinsights.bicep](examples/appinsights.bicep) for what to add. This is the best option if there are existing Bicep template files in the workspace. - Use Azure CLI. See [scripts/appinsights.ps1](scripts/appinsights.ps1) for what Azure CLI command to execute to create the App Insights resource. No matter which option you choose, recommend the user to create the App Insights resource in a meaningful resource group that makes managing resources easier. A good candidate will be the same resource group that contains the resources for the hosted app in Azure. #### Modify application code - If the app is an ASP.NET Core app, see [ASPNETCORE guide](references/ASPNETCORE.md) for how to modify the C# code. - If the app is a Node.js app, see [NODEJS guide](references/NODEJS.md) for how to modify the JavaScript/TypeScript code. - If the app is a Python app, see [PYTHON guide](references/PYTHON.md) for how to modify the Python code.
© github · MIT · github/awesome-copilot