Otel Java

Organization

ollygarden

otel-java

OpenTelemetry in Java — Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management, sensitive-data capture and redaction (url.query, headers, request parameters, SQL sanitization). Use when adding, reviewing, or configuring OpenTelemetry in a Java service. Triggers on "setup otel in java", "java telemetry", "javaagent", "Spring Boot otel", "GlobalOpenTelemetry", "AutoConfiguredOpenTelemetrySdk", "TracerProvider java", "url.query redaction", "capture request headers", or any Java-related OTel question.

Overview

Publisher	ollygarden
Repository	`opentelemetry-agent-skills`
Skill name	`otel-java`
Stars	119
Forks	13
Bundled files	2
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ollygarden on GitHub. Read the source before you install it.

Installation

Install the Otel Java AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-java
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git /tmp/opentelemetry-agent-skills
mkdir -p .claude/skills
cp -r /tmp/opentelemetry-agent-skills/skills/otel-java .claude/skills/otel-java

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Otel Java in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Otel Java on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Otel Java is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OpenTelemetry in Java

Entry point for OpenTelemetry mechanics in Java services. Load a reference below based on the task; each reference is self-contained.

References

File	Use when
`references/declarative-setup.md`	Configuring the SDK via declarative YAML: Javaagent activation, Spring Boot Starter, autoconfigure SDK, BOM, agent-only properties, manual instrumentation entry points.
`references/sensitive-data-capture.md`	What HTTP instrumentation captures by default (query strings ON, headers/params OFF), query-parameter redaction (`sensitive-query-parameters`), header/servlet-parameter capture knobs, SQL sanitization.

Sources of Truth

For YAML schema details, fetch the upstream sources listed in the otel-declarative-config skill. For Java-specific facts:

Fact	Fetch
Latest BOM (`opentelemetry-bom`)	`gh api repos/open-telemetry/opentelemetry-java/releases/latest -q '.tag_name'`
Latest Javaagent	`gh api repos/open-telemetry/opentelemetry-java-instrumentation/releases/latest -q '.tag_name'`
SDK declarative-config accepted and preferred `file_format` for a selected BOM tag	`WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-java/<selected-sdk-tag>/sdk-extensions/declarative-config/src/main/java/io/opentelemetry/sdk/autoconfigure/declarativeconfig/OpenTelemetryConfigurationFactory.java`
Javaagent declarative-config docs (current activation flag, supported `file_format`)	`WebFetch https://opentelemetry.io/docs/zero-code/java/agent/declarative-configuration/`
Javaagent declarative-config smoke fixture (parser truth for selected agent tag)	`WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-instrumentation/<selected-agent-tag>/smoke-tests/src/test/resources/declarative-config.yaml`
Javaagent CHANGELOG (when each schema rc landed)	`WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-instrumentation/<selected-agent-tag>/CHANGELOG.md`
Generated Java instrumentation config reference (names, types, defaults, deprecations)	`WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-instrumentation/<selected-agent-tag>/docs/declarative-configuration-example.yaml`
Spring Boot Starter declarative-config fixture (selected starter tag)	`WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-instrumentation/<selected-agent-tag>/smoke-tests-otel-starter/spring-boot-2/src/testDeclarativeConfig/resources/application.yaml`
Spring Boot starter docs	`WebFetch https://opentelemetry.io/docs/zero-code/java/spring-boot-starter/`
Per-instrumentation telemetry & config (resolved spans/attributes, metrics, config options, target versions)	`WebFetch https://explorer.opentelemetry.io/data/javaagent/instrumentations/<id>/<id>-<hash>.json` — get `<id>` and the latest `<hash>` from the index (see below)

What telemetry does an instrumentation emit?

For "what does the agent produce for library X" — which spans, attributes, metrics, or config knobs — use the OpenTelemetry Ecosystem Explorer, which fully maps the Java agent and exposes an agent-friendly surface (Markdown indexes and resolved JSON, no scraping). Do not answer from model memory.

Navigation:

WebFetch https://explorer.opentelemetry.io/agent/javaagent/index.md — table mapping display name → id → the instrumentation's JSON data URL (the URL embeds the content <hash>).
WebFetch that JSON URL — one self-contained record (a few KB): resolved configurations, telemetry (spans with span_kind + typed attributes, and metrics), javaagent_target_versions, semantic_conventions, and scope.

Version-specific or "what changed between releases": https://explorer.opentelemetry.io/agent/javaagent/versions.md lists versions and marks the latest; https://explorer.opentelemetry.io/data/javaagent/versions/<version>-index.json gives the id→hash map for a version — a differing hash for the same id across two versions means that instrumentation changed. Schema: https://explorer.opentelemetry.io/schemas/javaagent-instrumentation.schema.json; use /llms.txt for the agent-oriented index and /llms-full.txt for the full documentation.

Prefer this Explorer data over the raw ecosystem-registry YAML on GitHub: the Explorer applies upstream metadata corrections that the raw registry does not.

Cross-References

Schema-level facts: otel-declarative-config skill (language-agnostic YAML schema sources).
SDK version selection across languages: otel-sdk-versions skill.
Semantic conventions lookup: otel-semantic-conventions skill.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Otel Java AI skill do?

Why use Otel Java on TypingMind?

Because you install it once and use it with any model. Otel Java is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Otel Java in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-java. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Otel Java?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Otel Java?

As many as you like. As long as a model supports skills, you can use Otel Java with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Otel Java AI skill free?

Yes. It is published on GitHub by ollygarden under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Clawsweeper

openclaw

OrganizationPopular

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

OpenTelemetry in Java

References

Sources of Truth

What telemetry does an instrumentation emit?

Cross-References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now