otelyssey plugin
A marketplace of OpenTelemetry plugins for Claude Code, Codex, Copilot and other agents that checks and follows releases itself.
- 113 ★ on the repository
- Last commit
Extended access
Why this level
- Every plugin in the list comes from a third-party author and gets permissions in the agent client.
- Some plugins connect an agent to telemetry backends and read service logs and traces.
Install
- Works in
Manual install
claude plugin marketplace add using-system/otelysseyThe first command from the README; lines for Copilot, Codex and other clients differ and are given in the README.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Every plugin in the list comes from a third-party author and gets permissions in the agent client.
- Some plugins connect an agent to telemetry backends and read service logs and traces.
This is third-party code. Review the repository files before installing.
What it does
otelyssey connects to an agent client as a plugin marketplace in the Agent Plugins format, and every plugin in it is about OpenTelemetry: code instrumentation, semantic conventions, the Collector and backends that ingest telemetry. Installation starts with a command such as `claude plugin marketplace add using-system/otelyssey`. Plugins are grouped into sections: observing runs through telemetry, instrumentation and others. They include oddyssey, save-toolkit, the OllyGarden skill set and otel-instrumentation-skills. To add your own plugin, fill in an issue form: the repository checks it, lists it and follows new releases every night.
Who it is for. Observability and SRE engineers who connect instrumentation and telemetry analysis to Claude Code, Codex or Copilot without hunting for plugins across separate repositories.
Good fit when
- A service has to be covered with traces and metrics and a set of skills by language and semantic conventions is needed.
- An agent verifies a change against a local OpenTelemetry and Grafana stack rather than logs.
- A team chooses among several plugins on the topic and wants versions, stars and last-commit dates side by side.
- An author has an OpenTelemetry plugin and wants to show it to users of several agents at once.
Not a fit when
- The task has nothing to do with OpenTelemetry, since every plugin in the list covers only it.
- One specific plugin is wanted and it is easier to take straight from its repository.
- Policy forbids third-party plugins, because each one comes from its own author.
Example request
Install a plugin for instrumenting a Go service with OpenTelemetry and show which traces it will add.Limitations
The repository itself is only a catalogue: the code of each plugin belongs to its author and follows their rules. Read the plugin page and its permissions before installing. Add commands differ for Claude Code, Copilot, Codex, Grok, APM and Hermes, while lines for VS Code, Kiro, OpenClaw and Mistral Vibe appear on plugin pages. A new plugin joins the list after the automatic check of its submission, and versions in the list are refreshed by a nightly job, so a fresh release may appear with a delay.
How to disable. Remove the marketplace from the client, for example with `claude plugin marketplace remove using-system/otelyssey`, and disable the installed plugins separately.
FAQ
How do I add otelyssey to Claude Code?
Run `claude plugin marketplace add using-system/otelyssey`, then choose a plugin from the list and install it from the line on the plugin page.
Which clients does otelyssey support?
Claude Code, Copilot, Codex, Grok, APM and Hermes through the shared marketplace, and plugin pages give lines for VS Code, Kiro, OpenClaw and Mistral Vibe.
How do I add my own plugin to otelyssey?
Open the `submit-plugin` issue form in the repository. You need a public GitHub repository, a `plugin.json` in the Agent Plugins format and an OpenTelemetry subject. The rest is read from the file.
Does otelyssey follow new plugin versions?
Yes, once listed, the repository follows the plugin's releases every night.
What counts as an OpenTelemetry subject?
Instrumentation, semantic conventions, the Collector or a backend that ingests OpenTelemetry telemetry.
Discussion
No questions or reviews yet.
Related
PluginsOpenTelemetry Agent Skills helps agents instrument applications, configure Collector and check versions against primary sources.
An AWS marketplace of plugins that give the agent skills to architect, deploy and operate AWS services
OpenTelemetry-based CLI tracing for Claude Code, Cursor and Codex sessions, showing what the agent actually did and what it cost
A pattern library and skill set for recurring agent loops: issue triage, dependency cleanup, PR babysitting
Weaver validates, resolves and diffs OpenTelemetry semantic conventions, and its MCP mode feeds attribute names to your agent
The official Sentry skills: SDK setup for your platform, production error debugging with Seer, alerts and an OpenTelemetry exporter
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| otelyssey (this card) | no | 113 | |
| OpenTelemetry Agent Skills by OllyGarden | no | 125 | a single OpenTelemetry skill set; otelyssey gathers such sets and other plugins into a shared marketplace |
| Claude Code Marketplace | no | 686 | a general community marketplace of commands and agents; otelyssey holds only OpenTelemetry plugins |
README in short
The README opens with install commands for six clients and a plugin submission form, followed by an automatically built list with versions, stars and last-commit dates. Author requirements are a public repository, `plugin.json` and an OpenTelemetry subject.