Appinsights Instrumentation
MicrosoftOfficialCreated by Microsoft
- Skill
- Tool integration
- Cloud and DevOps
- MIT
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill serves as a comprehensive reference for developers looking to integrate Azure Application Insights into their web applications. It provides structured guidance on telemetry patterns, SDK configuration, and environment-specific setup requirements. The skill emphasizes best practices for observability, including when to leverage auto-instrumentation versus manual code modifications, and provides references for various programming languages and hosting environments.
What it does
- Explains concepts and best practices for Application Insights instrumentation.
- Provides guidance on selecting between auto-instrumentation and manual SDK integration.
- Offers reference material for configuring telemetry in ASP.NET Core, Node.js, and Python applications.
- Details the process for creating Application Insights resources via Bicep or Azure CLI.
- Provides quick references for OpenTelemetry SDKs and exporters.
- Outlines environment-specific observability strategies for Azure-hosted applications.
When to use it
- When you need to understand how to instrument a web application for monitoring.
- When you are researching telemetry patterns for Azure-hosted services.
- When you need specific SDK setup instructions for supported languages.
- When you need to determine the best instrumentation approach for your hosting environment.
Advantages
- Centralized reference for Azure Application Insights patterns and configurations.
- Clear distinction between automated and manual instrumentation workflows.
- Supports multiple programming languages and Azure hosting environments.
- Promotes modern configuration practices like using environment variables over deprecated files.
Usage examples
- “How do I manually instrument my Node.js app for Application Insights?”
- The agent provides the necessary steps to modify your Node.js code, including SDK installation and configuration patterns for Azure Monitor.
- “What are the best practices for instrumenting an ASP.NET Core app in Azure?”
- The agent explains the recommended approach using the Azure Monitor OpenTelemetry library and environment variables for connection strings.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/appinsights-instrumentation/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip appinsights-instrumentation.zip -d .agents/skills
Documentation by Microsoft
AppInsights Instrumentation Guide
This skill provides guidance and reference material for instrumenting webapps with Azure Application Insights.
⛔ ADDING COMPONENTS?
If the user wants to add App Insights to their app, invoke azure-prepare instead. This skill provides reference material—azure-prepare orchestrates the actual changes.
When to Use This Skill
User asks how to instrument (guidance, patterns, examples)
User needs SDK setup instructions
azure-prepare invokes this skill during research phase
User wants to understand App Insights concepts
When to Use azure-prepare Instead
User says "add telemetry to my app"
User says "add App Insights"
User wants to modify their project
Any request to change/add components
Prerequisites
The app in the workspace must be one of these kinds
An ASP.NET Core app hosted in Azure
An Azure Container App
A Node.js app hosted in Azure
A Python 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.
SDK Quick References
OpenTelemetry Distro: Python | TypeScript
Platform-Specific Guides
Container Apps: Observability Guide
Files
- ATTRIBUTION.mdAdded by AutoGineer1.1 KiB
- LICENSE.txt1.1 KiB
- SKILL.md3.7 KiB
- examples/appinsights.bicep759 B
- references/aspnetcore.md1.7 KiB
- references/auto.md891 B
- references/container-apps.md7.2 KiB
- references/nodejs.md1.8 KiB
- references/python.md1.8 KiB
- references/sdk/azure-monitor-opentelemetry-exporter-java.md1.1 KiB
- references/sdk/azure-monitor-opentelemetry-exporter-py.md963 B
- references/sdk/azure-monitor-opentelemetry-py.md880 B
- references/sdk/azure-monitor-opentelemetry-ts.md986 B
- scripts/appinsights.ps1Script1.2 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python
Security
What our scanner noticed· Low risk
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/azure-skills/skills/appinsights-instrumentation · commit 0696600
- Licence
- MIT License (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- microsoft/azure-skills
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download appinsights-instrumentation.zip