Index of every page on this site: llms.txt
All skills
github avatar

/appinsights-instrumentation

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/appinsights-instrumentation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈25 tokens for metadata: the name and description. ≈583 when used: this file. ≈1.6k more on demand in 4 files.

Description uses 1.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈101 characters, or 1.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert21d5 checks · Risk SAFE
  • Gen Agent Trust Hub21d

    This skill provides standard guidance for instrumenting web applications with Azure Application Insights using official Microsoft libraries and Azure CLI commands. No security risks were identified.

  • Socket21d

    No alerts

  • Snyk21d

    Risk: LOW · No issues

  • Runlayer9mo

    7/8 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 11 months ago
  • azure
  • app-insights
  • telemetry
  • observability
  • asp-net-core
  • node-js
  • instrumentation
  • monitoring

README badge

README badge for github/awesome-copilot/appinsights-instrumentation

Instruments ASP.NET Core or Node.js webapps hosted in Azure to send telemetry to Azure App Insights, with options for auto-instrumentation on App Service or manual setup via Bicep templates and code modifications.

Generated from the current SKILL.md.

Does this skill work with my hosting environment?
Yes, if your app is ASP.NET Core or Node.js hosted in Azure (App Service, Container Apps, or as code). Python apps are referenced in the guides but may have limited support. Apps hosted outside Azure are not supported.
Do I need to manually instrument, or can the skill do it automatically?
For ASP.NET Core apps on Azure App Service, the skill can auto-instrument using the AUTO guide. For other setups, you'll manually create an App Insights resource and modify your application code.
How do I create the App Insights resource?
You can add App Insights to an existing Bicep template (recommended if you have one), or use Azure CLI via the included PowerShell script. The skill recommends placing it in the same resource group as your hosted app.
What languages and frameworks does this support?
ASP.NET Core and Node.js are fully supported with code instrumentation guides. Python is referenced but support details are not specified in the skill description.

Generated from the current SKILL.md. These answers refresh after source changes.