azure-monitor-opentelemetry-exporter-java
Configure Azure Monitor Telemetry for Java
Java teams need clear guidance to send traces, metrics, and logs to Azure Monitor. This skill provides setup, span, metric, exception, and migration examples for OpenTelemetry-based observability.
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/azure-monitor-opentelemetry-exporter-java.md and its manifest at https://skillstore.io/api/skills/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". I need to send Java OpenTelemetry data to Azure Monitor.
Expected outcome:
The response explains the recommended autoconfigure package, the connection string environment variable, and the basic initialization flow.
Using "azure-monitor-opentelemetry-exporter-java". How should I record errors in spans?
Expected outcome:
The response describes recording the exception, setting an error status, rethrowing the exception, and ending the span safely.
Using "azure-monitor-opentelemetry-exporter-java". What should I change during migration?
Expected outcome:
The response identifies the deprecated dependency, recommends autoconfigure, and outlines initialization changes to review.
Security Audit
SafeThe reviewed skill is documentation for Azure Monitor OpenTelemetry Exporter usage and migration guidance. Static findings are false positives caused by Markdown code fences, Java examples, placeholder Azure URLs, and reference links; no prompt injection, credential access, command execution, or malicious intent was found.
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/azure-monitor-opentelemetry-exporter-java/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/azure-monitor-opentelemetry-exporter-java?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/azure-monitor-opentelemetry-exporter-java?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/azure-monitor-opentelemetry-exporter-java/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/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/azure-monitor-opentelemetry-exporter-java/audits/6BibTeX citation
@techreport{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/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-09"
url: "https://skillstore.io/skills/azure-monitor-opentelemetry-exporter-java/audits/6"
identifiers:
- type: other
value: "skillstore: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
Migrate a Java service
Plan a move from the deprecated Azure Monitor exporter package to the autoconfigure package.
Add basic tracing
Use span and attribute examples to add distributed tracing to a Java operation.
Improve production diagnostics
Record exceptions, metrics, and operation context for Azure Monitor troubleshooting.
Try These Prompts
Show me how to configure Azure Monitor OpenTelemetry for a Java service using the recommended autoconfigure package.
Help me add OpenTelemetry spans, attributes, and exception recording to a Java method that processes customer orders.
Compare the deprecated Azure Monitor OpenTelemetry exporter setup with the autoconfigure approach and give me a migration checklist.
Design a Java observability plan for Azure Monitor that covers traces, metrics, exception recording, span naming, and useful attributes.
Best Practices
- Use the autoconfigure package for new work because the exporter package is deprecated.
- Set meaningful span names and include useful attributes for troubleshooting.
- Record exceptions and end spans in finally blocks or try-with-resources scopes.
Avoid
- Starting new projects on the deprecated exporter package.
- Using vague span names that do not describe the operation.
- Adding sensitive customer data or secrets as span attributes.