otel-cli

Start a local OTLP server and query traces, logs, and metrics.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hrntknr/otel-cli --skill otel-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-cli
Source: https://github.com/hrntknr/otel-cli/tree/main/skills/otel-cli
Command: npx skills add https://github.com/hrntknr/otel-cli --skill otel-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenTelemetry data is often scattered across services and it can be hard to run a local collector to observe traces, logs, and metrics during development. This skill provides a self-contained local OTLP server with built-in query capabilities to quickly inspect observable data.

Core Features & Use Cases

  • Start a local OTLP server to collect traces, logs, and metrics for debugging.
  • Query traces, logs, and metrics from the in-memory store with filtering and time ranges.
  • Attach to or view a running server and follow real-time data to validate observability during development.

Quick Start

Start the local OTLP server with otel-cli server --no-tui and begin querying traces, logs, and metrics to verify observability data.

Frequently Asked Questions about otel-cli

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

FAQPage Schema
How do I debug OpenTelemetry traces and logs locally during development?

You can debug OpenTelemetry traces and logs locally by starting a self-contained local OTLP server to collect, query, and inspect observable data in real-time. This allows you to validate observability outputs directly during your development workflow.

Can I query OpenTelemetry metrics with filtering and time ranges from a local server?

Yes, you can query OpenTelemetry metrics, traces, and logs from an in-memory local server store using specific filters and time ranges. This enables precise inspection of observability data generated during local application testing.

What is the best way to validate observability outputs in real-time while coding?

The best way to validate observability outputs is to start a local OTLP server and attach to it in real-time follow mode. This captures live traces, logs, and metrics, allowing you to verify data as your application executes locally.

Do I need a remote collector to inspect and troubleshoot OpenTelemetry data?

No, you do not need a remote collector to inspect and troubleshoot OpenTelemetry data. You can run a local OTLP server with built-in query capabilities to quickly observe and debug traces, logs, and metrics in-memory.

Why are my OpenTelemetry traces scattered across services and hard to observe during development?

OpenTelemetry traces are often scattered across services, making them hard to observe without a centralized collector. Starting a local OTLP server resolves this by aggregating and querying your local observability data in a single in-memory store.