azure-monitor-opentelemetry-exporter-java
Instrument Java Services with Azure Monitor
Manual Azure Monitor instrumentation can make Java telemetry setup and migration difficult. This skill provides focused OpenTelemetry examples for traces, metrics, exceptions, and exporter configuration.
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-exporter-java" from https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-exporter-java.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-monitor-opentelemetry-exporter-java/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-exporter-java". Help me configure Azure Monitor telemetry for a new Java service.
Expected outcome:
- Recommendation: use Azure Monitor OpenTelemetry Autoconfigure because the standalone exporter is deprecated.
- Configuration: supply the Application Insights connection string through an environment variable.
- Validation: confirm test spans appear in Application Insights before rollout.
Using "azure-monitor-opentelemetry-exporter-java". How should I trace an order processing operation?
Expected outcome:
- Create one parent span for order processing and child spans for significant downstream operations.
- Add stable attributes such as order identifier, item count, and customer tier.
- Record exceptions, set error status, and end every span in a finally block.
Using "azure-monitor-opentelemetry-exporter-java". Plan migration from the deprecated Azure Monitor exporter.
Expected outcome:
- Replace the exporter dependency with the autoconfigure package.
- Update initialization while preserving environment-based connection string handling.
- Compare trace and metric delivery in a test environment before removing the previous configuration.
Security Audit
SafeAll 42 static findings are false positives caused by Markdown backticks, documentation links, metric labels, package paths, and ordinary Java method declarations. The skill contains inert guidance and sample code, with no command execution, credential access, reconnaissance, prompt injection, or malicious intent.
Risk Factors
⚙️ External commands (26)
🌐 Network access (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-exporter-java/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-exporter-java?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-exporter-java?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-monitor-opentelemetry-exporter-java/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-monitor-opentelemetry-exporter-java.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-exporter-java security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-exporter-java/audits/6BibTeX citation
@techreport{sickn33-sickn33-azure-monitor-opentelemetry-exporter-java-2026,
author = {sickn33},
title = {azure-monitor-opentelemetry-exporter-java security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-exporter-java/audits/6},
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-exporter-java security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-monitor-opentelemetry-exporter-java/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-azure-monitor-opentelemetry-exporter-java:audit:6"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-azure-monitor-opentelemetry-exporter-java
2026-08-22
azure-monitor-opentelemetry-exporter-java
2026-08-22
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Add Java Tracing
Create spans, attributes, nested operations, and exception records for a Java service.
Standardize Azure Telemetry
Plan consistent OpenTelemetry initialization and custom span processing across managed Java services.
Migrate Deprecated Exporters
Replace the standalone Azure Monitor exporter with the recommended autoconfigure package.
Try These Prompts
Show the recommended Azure Monitor OpenTelemetry setup for my Java service using an environment variable connection string.
Design spans and useful attributes for this Java operation: [describe operation]. Include exception handling and reliable span completion.
Propose OpenTelemetry counters and histograms for [service workflow]. Include metric names, units, and low-cardinality attributes.
Review my current Azure Monitor exporter setup: [describe setup]. Create a migration plan for autoconfigure, including validation and rollback steps.
Best Practices
- Use autoconfigure for new implementations and migrations.
- Use meaningful span names and low-cardinality attributes that support diagnosis.
- Record exceptions and always end spans through reliable scope management.
Avoid
- Do not start new projects with the deprecated standalone exporter.
- Do not place real Application Insights connection strings in source files or prompts.
- Do not add unbounded values to metric attributes or span dimensions.