Master OpenTelemetry in Java with the otel-java Skill

Where this fits

You’re a Java developer who just added OpenTelemetry to a Spring Boot service, but the traces are missing query parameters, or the SQL statements are leaking PII. You need to quickly configure the Javaagent, set up redaction rules, and ensure the SDK is wired correctly—without reading hundreds of pages of docs. The otel-java skill gives your AI agent a structured reference to handle exactly these tasks, from zero-code instrumentation to sensitive-data capture.

Why agents benefit

• Zero-code setup guidance: The skill knows the exact flags and environment variables for the Javaagent, so your agent can generate a working -javaagent command or OTEL_* config without guessing.
• Declarative YAML mastery: It references the declarative configuration format, letting agents produce valid YAML for resource attributes, exporters, and samplers—no more trial-and-error.
• Sensitive-data redaction: With dedicated references for url.query, headers, request parameters, and SQL sanitization, agents can implement redaction rules that meet compliance requirements.
• Framework-specific advice: The skill distinguishes between Spring Boot Starter, manual autoconfigure SDK, and agent-only setups, so agents recommend the right entry point for your project.
• Dependency management: It knows the correct BOM versions and artifact coordinates, reducing build failures from mismatched OpenTelemetry libraries.

Practical scenarios

Diagnosing missing trace context in a microservice

Your agent uses the skill to check if the Javaagent is properly attached and whether the OTEL_SERVICE_NAME and exporter endpoints are set. It then suggests adding the Spring Boot Starter for automatic instrumentation, and validates the pom.xml BOM version.

Redacting sensitive data from HTTP spans

A payment service is capturing full credit card numbers in url.query. The agent pulls the sensitive-data reference, shows how to set OTEL_INSTRUMENTATION_HTTP_CAPTURE_HTTP_QUERY to a sanitized pattern, and adds a server-side span processor to strip headers.

Migrating from manual SDK to Javaagent

You have a custom AutoConfiguredOpenTelemetrySdk setup that’s brittle. The agent explains the trade-offs, provides a YAML-based declarative config, and lists the properties that only work with the Javaagent—ensuring a smooth transition without losing custom spans.

Add it to your agent workflow

Install the skill with:

npx skills add ollygarden/opentelemetry-agent-skills --skill otel-java

Then ask your agent: “Set up OpenTelemetry in my Spring Boot app with Javaagent, capture request headers, and redact all query parameters.” The agent will load the relevant reference files and produce a step-by-step configuration, including pom.xml dependencies and environment variables.

Compare before adopting

Before committing, compare otel-java against:

• Quality signals: Check the GitHub repo’s stars (currently 97), recent commits, and whether the skill is maintained alongside OpenTelemetry spec changes.
• Alternatives: Other agent skills might cover generic observability, but this one is Java-specific and includes redaction details that generic ones miss.
• Workflow fit: Verify that the skill’s triggers match your typical queries—e.g., “java telemetry” or “url.query redaction”—so your agent actually picks it up.

Why it is worth tracking

This skill is a strong indicator of the growing ecosystem for agent-based infrastructure configuration. Its focused scope, active author, and practical references make it a reliable resource for any Java/OpenTelemetry task. Track it because observability configuration is a recurring pain point, and having a skill that encodes best practices—especially around sensitive data—saves time and reduces errors. For a deeper look at this skill’s capabilities, see the OpenAgentSkill listing.