Back to catalog / Integrations
App Insights: identify hosting before choosing auto or SDK instrumentation
Identify language, framework, and hosting before choosing auto or SDK instrumentation.
Skills
Read the source references for auto, ASP.NET, Node, or Python instrumentation. Confirm language/framework and whether the app runs as code, container, or App Service; ask about hosting. For ASP.NET Core on App Service, assess auto-instrumentation first; otherwise follow the official OpenTelemetry distro/exporter guide. Prefer existing Bicep for a new Insights resource or inspect the Azure CLI script before execution. For guidance-only requests, report a plan; route actual component/resource changes to azure-prepare with scope confirmation.
Permissions
Prerequisites
- Plan Application Insights instrumentation for Azure-hosted ASP.NET Core, Node, Python, or Container Apps.
Permissions
- May create monitoring resources and edit app code; clarify hosting context first.
Limitations
This is guidance; use azure-prepare for implementation, with authorization for resource/code changes.
Pinned upstream source
- Repository
- microsoft/skills
- File path
- .github/plugins/azure-skills/skills/appinsights-instrumentation/SKILL.md
- Pinned commit
fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Application Insights docs · Azure Monitor OpenTelemetry SDKs · azure-prepare handoff
Main topic
Take a coding Agent change from context to verification