otelux

v0.1.5

Investigate local OpenTelemetry traces, logs, metrics, errors, and latency with OTelux.

CodexClaude Code4 Skills1 MCP serverstdio

By OTelux contributorsLicense: MIT3 GitHub starsUpdated 2 days ago

Directory evidence

Runtimes: Codex and Claude Code
Parsed components: 5 skill or MCP entries
Source updated: Sep 22, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install otelux for Codex and Claude Code

Installs for the current user

codex plugin marketplace add b1tank/otelux
codex plugin marketplace upgrade otelux-plugins
codex plugin add otelux@otelux-plugins

Paste and run these commands in a terminal with Codex. They add and refresh the otelux-plugins catalog, then install this plugin.

Compatibility: the page URL and API slug “otelux” remain stable.

Codex: otelux@agent-plugin-marketplace → otelux@otelux-plugins

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/b1tank/otelux

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/otelux/.

Plugin files

plugins/otelux/

├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/analyze-trace/SKILL.md
├── skills/investigate-incident/SKILL.md
├── skills/open-dashboard/SKILL.md
├── skills/service-health/SKILL.md
└── .mcp.json

Included Skills4

analyze-traceskills/analyze-trace/SKILL.md

Analyze an OpenTelemetry trace or slow request from OTelux, including critical path, errors, span attributes, and correlated logs. Use when: given a trace ID, investigating a slow trace, or explaining a distributed request waterfall.

investigate-incidentskills/investigate-incident/SKILL.md

Investigate recent application errors, failures, regressions, or incidents using local OTelux traces and logs. Use when: something broke, requests are failing, an error appeared, or the user wants an evidence-backed incident summary.

open-dashboardskills/open-dashboard/SKILL.md

Hand off an observability investigation to the OTelux visual desktop dashboard. Use when: the user wants a trace waterfall, logs table, metrics chart, dashboard, or a visual view of telemetry.

service-healthskills/service-health/SKILL.md

Summarize local service health from OTelux traces, errors, latency, and logs. Use when: asking what services are active, which service is unhealthy or slow, or requesting an observability status report.

MCP servers1

oteluxstdio

command: node
args: ./bin/otelux-mcp-bridge.mjs
cwd: .

Plugin manifests2

plugins/otelux/.codex-plugin/plugin.json

{
  "name": "otelux",
  "version": "0.1.5",
  "description": "Investigate local OpenTelemetry traces, logs, metrics, errors, and latency with OTelux.",
  "author": {
    "name": "OTelux contributors",
    "url": "https://github.com/b1tank/otelux"
  },
  "homepage": "https://github.com/b1tank/otelux",
  "repository": "https://github.com/b1tank/otelux",
  "license": "MIT",
  "keywords": [
    "opentelemetry",
    "observability",
    "tracing",
    "logs",
    "metrics",
    "debugging"
  ],
  "skills": "./skills/",
  "mcpServers": "./.mcp.codex.json",
  "interface": {
    "displayName": "OTelux",
    "shortDescription": "Analyze local OpenTelemetry data",
    "longDescription": "Query the OTelux desktop store through read-only MCP tools, investigate incidents and slow traces, summarize service health, and hand off evidence to the visual OTelux workbench.",
    "developerName": "OTelux contributors",
    "category": "Developer Tools",
    "capabilities": [
      "Read"
    ],
    "websiteURL": "https://github.com/b1tank/otelux",
    "privacyPolicyURL": "https://github.com/b1tank/otelux/blob/main/docs/privacy.md",
    "defaultPrompt": [
      "Use OTelux to investigate recent errors and identify the most likely root cause.",
      "Use OTelux to find the slowest local traces and explain their critical paths.",
      "Summarize service health from the telemetry currently stored in OTelux."
    ],
    "brandColor": "#7AA2F7"
  }
}

plugins/otelux/.claude-plugin/plugin.json

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "otelux",
  "displayName": "OTelux",
  "version": "0.1.5",
  "description": "Investigate local OpenTelemetry traces, logs, metrics, errors, and latency with OTelux.",
  "author": {
    "name": "OTelux contributors",
    "url": "https://github.com/b1tank/otelux"
  },
  "homepage": "https://github.com/b1tank/otelux",
  "repository": "https://github.com/b1tank/otelux",
  "license": "MIT",
  "keywords": [
    "opentelemetry",
    "observability",
    "tracing",
    "logs",
    "metrics",
    "debugging"
  ],
  "skills": "./skills/",
  "mcpServers": "./.mcp.json"
}