Help us improve
Share bugs, ideas, or general feedback.
From azure
Guides instrumenting ASP.NET Core and Node.js webapps hosted in Azure with Application Insights telemetry. Covers SDK setup, patterns, auto-instrumentation, and resource creation.
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin microsoft-azure-skills-10How this skill is triggered — by the user, by Claude, or both
Slash command
/azure:appinsights-instrumentationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides **guidance and reference material** for instrumenting webapps with Azure Application Insights.
Guides instrumenting ASP.NET Core and Node.js webapps in Azure with Application Insights, covering SDK setup, telemetry patterns, auto-instrumentation, and config references.
One-line setup for Azure Application Insights with OpenTelemetry auto-instrumentation in Python. Covers configuration, custom traces/metrics/logs, sampling, and web framework integration (Flask, Django, FastAPI).
Configures Azure Monitor OpenTelemetry for Python apps with one-line auto-instrumentation to Application Insights for traces, metrics, and logs. Use for quick telemetry setup in Flask, Django, or FastAPI.
Share bugs, ideas, or general feedback.
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.
The app in the workspace must be one of these kinds
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.).
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 the app by creating the AppInsights resource and update the app's code.
Use one of the following options that fits the environment.
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.