azure-monitor-opentelemetry-ts
Instrument Node.js Apps with Azure Monitor
Adding reliable telemetry to Node.js services requires correct initialization, exporters, and lifecycle handling. This skill provides focused Azure Monitor OpenTelemetry patterns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-monitor-opentelemetry-ts" from https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-monitor-opentelemetry-ts/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.
Test it
Using "azure-monitor-opentelemetry-ts". Add Azure Monitor to an Express service using automatic instrumentation.
Expected outcome:
- Install the Azure Monitor OpenTelemetry distribution.
- Load monitoring before Express and other instrumented modules.
- Read the Application Insights connection string from the environment.
- Flush telemetry during graceful shutdown.
Using "azure-monitor-opentelemetry-ts". Recommend telemetry for a background order processor.
Expected outcome:
- Create spans for order validation, payment, and fulfillment.
- Record an order counter and processing duration histogram.
- Attach low-cardinality status and operation attributes.
- Record exceptions and close every span.
Using "azure-monitor-opentelemetry-ts". Assess a high-traffic service configuration.
Expected outcome:
Use representative sampling, verify offline storage limits, avoid sensitive dimensions, monitor exporter failures, and flush buffered telemetry before process exit.
Security Audit
SafeAll 52 static findings are false positives caused by Markdown code fences, expected Azure Monitor examples, and OpenTelemetry method names. The skill contains documentation only, with no executable scripts, prompt injection, credential harvesting, or undeclared network destination.
Risk Factors
⚙️ External commands (34)
🌐 Network access (1)
🔑 Env variables (10)
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.
Copy report link
https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-monitor-opentelemetry-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-monitor-opentelemetry-ts.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
sickn33. (2026). azure-monitor-opentelemetry-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-monitor-opentelemetry-ts-2026,
author = {sickn33},
title = {azure-monitor-opentelemetry-ts security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-monitor-opentelemetry-ts security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-ts/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-monitor-opentelemetry-ts:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Add Basic Service Telemetry
Configure automatic tracing, metrics, and logs for an existing Node.js service.
Standardize Observability Setup
Create a consistent Azure Monitor configuration for multiple Node.js workloads.
Tune Production Telemetry
Adjust sampling, storage, custom dimensions, and shutdown behavior for reliable operations.
Try These Prompts
Show me how to add Azure Monitor automatic instrumentation to my Node.js service. Include installation, initialization order, and required environment variables.
Design custom OpenTelemetry traces and metrics for these operations: [operations]. Include useful attributes, counters, histograms, and error recording.
Plan a manual Azure Monitor export pipeline for traces, metrics, and logs. Use these constraints: [runtime, modules, traffic, storage].
Review my Azure Monitor OpenTelemetry approach for production. Assess initialization, sampling, offline storage, sensitive attributes, failure handling, and graceful shutdown.
Best Practices
- Initialize Azure Monitor before importing instrumented application modules.
- Keep connection strings in managed environment settings and exclude secrets from telemetry attributes.
- Tune sampling and offline storage for traffic volume, reliability needs, and telemetry cost.
Avoid
- Do not initialize monitoring after application libraries have already loaded.
- Do not attach credentials, personal data, or unbounded values to spans and metrics.
- Do not terminate the process before buffered telemetry has been flushed.