otel-java

Fix OpenTelemetry SDK and Java agent instrumentation for traces, metrics, and logs.

2|Updated May 28, 2026
One-click install
npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-java
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-java
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/otel-java
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-java

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you correctly set up and repair OpenTelemetry instrumentation in Java so traces, metrics, and logs reliably appear and connect in Tsuga.

Core Features & Use Cases

  • Java OTel setup & auditing: guide programmatic SDK configuration, Java agent usage, and JVM resource attribute choices.
  • Signal coverage for JVM apps: covers traces, metrics, logs, and context/resource handling for Java, Kotlin, and Scala services (including Spring Boot, Quarkus, Micronaut, Vert.x, Kafka consumers, and gRPC).
  • Quality guardrails: enforces a mutation gate for proposed code changes and highlights common correctness issues (scope management, span lifecycle, protocol/endpoint pitfalls, and semantic convention mistakes).
  • Post-deploy verification workflow: directs you to run Tsuga smoke tests and use Tsuga queries when signals are missing or disconnected.

Quick Start

Use the otel-java skill to fix missing or broken OpenTelemetry instrumentation in a Java service using the Java agent or the programmatic SDK so traces appear in Tsuga with correct service attributes.

Frequently Asked Questions about otel-java

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix missing OpenTelemetry traces in my Spring Boot application?

Missing OpenTelemetry traces in Spring Boot typically stem from incorrect Java agent attachment, SDK misconfiguration, or resource attribute gaps. This skill audits instrumentation and remediates span lifecycle and endpoint issues to produce queryable traces.

Does the OpenTelemetry Java agent support Kafka consumers and gRPC instrumentation?

Yes, the OpenTelemetry Java agent supports Kafka consumers, JMS, SQS, RabbitMQ, and gRPC. This skill provides version-aligned guidance for opentelemetry-bom and -alpha instrumentation artifacts to ensure signals are correctly produced for these frameworks.

What is the best way to configure OpenTelemetry metrics and logs for JVM services?

The best way to configure OpenTelemetry metrics and logs for JVM services is through programmatic SDK configuration alongside the Java agent. This skill enforces semantic conventions and applies a confirmation mutation gate for safe code changes.

Why are my OpenTelemetry spans disconnected when using Quarkus or Micronaut?

Disconnected OpenTelemetry spans in Quarkus or Micronaut often result from context propagation errors or mismatched -alpha instrumentation artifact versions. This skill audits scope management and aligns versions to connect traces properly.

Can I set up OpenTelemetry from scratch for a Kotlin service using Vert.x?

Yes, you can set up OpenTelemetry from scratch for Kotlin services using Vert.x. This skill covers setup-from-scratch workflows including JVM resource attribute choices, Java agent usage, and protocol configuration for Kotlin applications.

How do I verify OpenTelemetry signals are queryable after deploying my Java service?

To verify OpenTelemetry signals are queryable after deployment, run Tsuga smoke tests and use Tsuga queries to check for missing or disconnected traces, metrics, and logs. This skill directs that post-deploy verification workflow to confirm signal correctness.