Skills

Skill 19 of 200

AppInsights Instrumentation

Instrument a webapp to send useful telemetry data to Azure App Insights

2 minutes · 351 words · 8 sections

Install

$ npx skills add github/awesome-copilot --skill appinsights-instrumentation

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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

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 (opens in a new tab) 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 (opens in a new tab) 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 (opens in a new tab) 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 (opens in a new tab) for how to modify the C# code.
If the app is a Node.js app, see NODEJS guide (opens in a new tab) for how to modify the JavaScript/TypeScript code.
If the app is a Python app, see PYTHON guide (opens in a new tab) for how to modify the Python code.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “AppInsights instrumentation”, a leading h1 that duplicated the skill title.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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

Add AppInsights to existing Bicep template. See examples/appinsights.bicep (opens in a new tab) 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 (opens in a new tab) for what Azure CLI command to execute to create the App Insights resource.

Modify application code

If the app is an ASP.NET Core app, see ASPNETCORE guide (opens in a new tab) for how to modify the C# code.
If the app is a Node.js app, see NODEJS guide (opens in a new tab) for how to modify the JavaScript/TypeScript code.
If the app is a Python app, see PYTHON guide (opens in a new tab) for how to modify the Python code.

AppInsights Instrumentation

When to use this skill

Prerequisites

Guidelines

Collect context information

Prefer auto-instrument if possible

Manually instrument

Create AppInsights resource

Modify application code

Colophon

AppInsights Instrumentation

When to use this skill

Prerequisites

Guidelines

Collect context information

Prefer auto-instrument if possible

Manually instrument

Create AppInsights resource

Modify application code

Appendix 19.1–19.7

ReferencesMarkdown · 4 files

ScriptsPowerShell · 1 file

Also bundled2 files

Colophon

Appendix 19.1–19.7

ReferencesMarkdown · 4 files

ScriptsPowerShell · 1 file

Also bundled2 files