Skip to content
cccskills
FreePublished on GitHub

obz-jaeger

Jaeger provider for obz. Covers trace search, trace retrieval by ID, and extension commands for service and operation discovery. This skill should be used when the user mentions "Jaeger", "obz trace -p jg", or needs to search distributed traces from a Jaeger backend.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

obz-jaeger: Jaeger Provider

Quick Reference

FieldValue
Aliasesjg, jaeger
SignalTrace
Query languageNone (query is a service name)
AuthBearer token or Basic auth
Provider flagsNone
Supported cmdssearch, get, services, operations

Supported Commands

Core trace commands

obz trace search      # Search traces by service name
obz trace get         # Retrieve a single trace by ID

Extension commands

obz trace services    # List all known service names
obz trace operations  # List operations for a given service (requires --service)

Authentication

Configure auth in config.yaml under providers.<name>.auth. Supports bearer token, basic auth, or no auth.

# config.yaml
providers:
  jg:
    endpoint: http://localhost:16686
    auth:
      token: ${env:JAEGER_TOKEN}

Then query with just -p:

obz trace search -p jg -q 'frontend' --from now-1h

Query Format

The -q value is a plain service name. Jaeger doesn't have a structured trace query language for searches.

obz trace search -p jg -q 'frontend' --from now-1h

Examples

Search traces for a service:

obz trace search -p jg -q 'frontend' --from now-1h

Retrieve a specific trace by ID:

obz trace get -p jg abc123def456

List all services:

obz trace services -p jg

List operations for a service:

obz trace operations -p jg --service frontend

Jaeger vs VictoriaTraces

Both providers speak the same Jaeger HTTP Query API and expose the same set of commands. The key difference is the backend:

AspectJaegerVictoriaTraces
StorageConfigurableBuilt-in
Default port1668610428
API compatibilityNativeJaeger-compatible

Choose jg when pointing at a standalone Jaeger deployment. Choose vt for VictoriaTraces.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Multi-backend observability CLI for querying metrics, logs, and traces across 12 backends. This skill should be used when the user runs obz commands, constructs metric/log/trace queries, configures providers, parses obz JSON output, or troubleshoots obz errors. Covers all core commands (metric query/list/info/labels/label-values/series, log search, trace search/get), global flags, time formats, output modes, config files, and exit codes.

The English summary is being prepared. Showing the original description.

alibaba/obz-cli28Updated Jul 12, 2026

obz-dd

Free

Datadog provider for obz. Supports metrics (Datadog Query Language), logs (Datadog Log Query), and traces. Requires api-key and app-key configured under auth in config.yaml. Does not support metric labels, label-values, or series commands. This skill should be used when the user mentions "Datadog", "DD", "obz -p dd", Datadog Query Language, or needs to configure Datadog provider instances with regional endpoints.

The English summary is being prepared. Showing the original description.

alibaba/obz-cli28Updated Jul 12, 2026

Elasticsearch provider for obz. Supports log search and trace operations using Elasticsearch Query DSL (Lucene-based). Requires --index flag. This skill should be used when the user mentions "Elasticsearch", "obz -p es", or needs to search logs or traces from an Elasticsearch cluster.

The English summary is being prepared. Showing the original description.

alibaba/obz-cli28Updated Jul 12, 2026

GreptimeDB provider for obz. Covers PromQL metric query, labels, label-values, and series commands via GreptimeDB's Prometheus-compatible API. Use this skill when the user mentions "GreptimeDB", "Greptime", "obz metric -p greptimedb", or needs to query metrics stored in a GreptimeDB instance.

The English summary is being prepared. Showing the original description.

alibaba/obz-cli28Updated Jul 12, 2026

Grafana Loki provider for obz. Covers log search using LogQL, a label-based query language for log aggregation. This skill should be used when the user mentions "Loki", "Grafana Loki", "LogQL", "obz log search -p loki", or needs to search logs from a Loki instance.

The English summary is being prepared. Showing the original description.

alibaba/obz-cli28Updated Jul 12, 2026

Grafana Mimir provider for obz. Covers all 6 metric commands using standard PromQL. Mimir is a horizontally-scalable Prometheus-compatible TSDB. This skill should be used when the user mentions "Mimir", "Grafana Mimir", "obz metric -p mimir", or needs to query metrics from a Mimir cluster.

The English summary is being prepared. Showing the original description.

alibaba/obz-cli28Updated Jul 12, 2026

See all skills by alibaba

Report a problem with this skill