mcpField
A
appinsights-instrumentation

appinsights-instrumentation

github.com/githubCloud & DevOps40.5k9.5k installsUpdated 1d ago
Repository

About appinsights-instrumentation

A skill for adding Azure Application Insights telemetry to supported web apps, aimed at teams seeking application health observability. It guides setup according to the app's language, framework, and hosting environment, with automatic instrumentation preferred when applicable.

Key features

  1. 01Determine app language, framework, and hosting
  2. 02Guide automatic instrumentation when applicable
  3. 03Create an App Insights resource
  4. 04Update ASP.NET Core or Node.js app code

Use cases

  1. 01Adding telemetry to an Azure-hosted ASP.NET Core app
  2. 02Instrumenting a Node.js app hosted in Azure
  3. 03Choosing resource creation steps for an app environment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/github/awesome-copilot --skill appinsights-instrumentation

After installing, type/appinsights-instrumentationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

LICENSE.txt
examples/
appinsights.bicep
references/
ASPNETCORE.md
AUTO.md
NODEJS.md
PYTHON.md
scripts/
appinsights.ps1

Details

From the project README

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

Comments

Markdown supported