Skills appinsights-instrumentation

📦

appinsights-instrumentation

Name: appinsights-instrumentation
Author: microsoft

v0.0.0-placeholder Content revision r2 Safe 📁 Filesystem access🌐 Network access⚙️ External commands🔑 Env variables

Instrument Apps with Azure Application Insights

Application teams need consistent telemetry setup across languages and Azure hosting services. This skill provides targeted SDK, infrastructure, environment, and query guidance for Application Insights.

Supports: Claude Codex Code(CC)

🥇 84 Gold

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "appinsights-instrumentation" from https://skillstore.io/skills/microsoft-appinsights-instrumentation.md and its manifest at https://skillstore.io/api/skills/microsoft-appinsights-instrumentation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/microsoft-appinsights-instrumentation.md Signed manifest GET /api/skills/microsoft-appinsights-instrumentation/manifest Signed lockfile GET /api/skills/microsoft-appinsights-instrumentation/lockfile

Test it

Using "appinsights-instrumentation". Should I instrument an ASP.NET Core app hosted on Azure App Service automatically or with the SDK?

Expected outcome:

Check whether the runtime and App Service configuration support portal auto-instrumentation.
Prefer automatic instrumentation when supported and no custom telemetry pipeline is required.
Use the SDK when custom spans, processors, or application-level controls are needed.

Using "appinsights-instrumentation". What should I configure for Application Insights in a Node.js service?

Expected outcome:

Install the Azure Monitor OpenTelemetry package.
Load configuration before initializing telemetry, then initialize before other instrumented modules.
Provide the connection string through deployment configuration or a managed secret reference.
Deploy and verify requests, dependencies, exceptions, and service role names.

Using "appinsights-instrumentation". How can I investigate repeated restarts in Azure Container Apps?

Expected outcome:

Review built-in restart metrics and Container Apps system logs.
Group restart events by application and revision over a relevant time window.
Correlate revision changes with console errors, scaling activity, and trace failures.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

The reviewed patterns are documentation and examples for Azure Application Insights. Relative links, Azure CLI substitutions, portal URLs, and environment reads do not demonstrate traversal, reconnaissance, or unauthorized secret access. No prompt injection or malicious intent was found.

Files scanned

570

Lines analyzed

Review items

False positives ignored

Risk Factors

📁 Filesystem access (2)

references/aspnetcore.md:19 references/aspnetcore.md:27

🌐 Network access (2)

references/auto.md:10 references/container-apps.md:81

⚙️ External commands (2)

references/container-apps.md:10-12 references/container-apps.md:14-16

🔑 Env variables (3)

references/nodejs.md:15 references/sdk/azure-monitor-opentelemetry-ts.md:15 references/sdk/azure-monitor-opentelemetry-ts.md:15

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/microsoft-appinsights-instrumentation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/microsoft-appinsights-instrumentation/security.svg)](https://skillstore.io/skills/microsoft-appinsights-instrumentation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/microsoft-appinsights-instrumentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/microsoft-appinsights-instrumentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/microsoft-appinsights-instrumentation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

microsoft. (2026). appinsights-instrumentation security audit report (audit version 5) [Author version 0.0.0-placeholder]. Skillstore. https://skillstore.io/skills/microsoft-appinsights-instrumentation/audits/5

BibTeX citation

@techreport{microsoft-microsoft-appinsights-instrumentation-2026,
  author = {microsoft},
  title = {appinsights-instrumentation security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/microsoft-appinsights-instrumentation/audits/5},
  note = {Author version 0.0.0-placeholder}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "appinsights-instrumentation security audit report (audit version 5)"
version: "0.0.0-placeholder"
type: report
authors:
  - name: "microsoft"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/microsoft-appinsights-instrumentation/audits/5"
identifiers:
  - type: other
    value: "skillstore:microsoft-appinsights-instrumentation:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan SDK Instrumentation

Select the appropriate Application Insights setup and initialization order for a supported application stack.

Configure Azure Observability

Plan Application Insights, Log Analytics, environment variables, and infrastructure changes for an Azure workload.

Diagnose Container Apps

Use metrics, logs, traces, and KQL guidance to assess Azure Container Apps observability.

Try These Prompts

Choose an Instrumentation Method

Explain whether my [language] application hosted on [service] supports automatic instrumentation. Compare it with manual SDK setup.

Create a Manual Setup Plan

Plan Application Insights instrumentation for my [framework] application on [Azure service]. Include package, initialization, configuration, and deployment steps.

Review Azure Infrastructure

Review my Application Insights and Log Analytics design for [workload]. Identify required Bicep or Azure CLI changes and configuration risks.

Design Distributed Observability

Design tracing and diagnostics for [services] on Azure Container Apps. Cover correlation, sampling, Dapr, role naming, and useful KQL investigations.

Best Practices

Confirm the application language, framework, and hosting environment before choosing an instrumentation method.
Keep connection values in managed configuration or secret references, and never commit real values.
Initialize telemetry early, then validate traces, dependencies, logs, sampling, and service identity after deployment.

Avoid

Do not hardcode connection values in source files or infrastructure examples.
Avoid full production sampling without evaluating traffic volume, cost, and diagnostic requirements.
Do not treat infrastructure metrics as a replacement for application traces and dependency telemetry.