Menu
VictoriaTraces (OTLP ingest, Jaeger-compatible query) on the yai stack — which services emit traces, HTTP API recipes, OTLP endpoint. Auto-load on VictoriaTraces, vtraces, OTLP, trace, Jaeger, span questions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | vtraces |
| description | VictoriaTraces (OTLP ingest, Jaeger-compatible query) on the yai stack — which services emit traces, HTTP API recipes, OTLP endpoint. Auto-load on VictoriaTraces, vtraces, OTLP, trace, Jaeger, span questions. |
| when_to_use | Load when the user asks about distributed tracing, OTLP configuration, trace correlation, Jaeger API queries, or wants to find slow spans in a specific service. Also load when wiring LiteLLM or Langfuse to emit traces to VictoriaTraces. |
| allowed-tools | Bash(curl *) |
OTLP ingest + Jaeger-compatible query API. URL in env: YAI_VTRACES_URL
(port 21428).
# Jaeger endpoint (for Grafana datasource and queries)
YAI_VTRACES_JAEGER_URL="${YAI_VTRACES_URL}/select/jaeger"
# OTLP ingest (from other services)
http://localhost:21428/insert/opentelemetry/v1/traces
# From inside another compose network:
http://host.docker.internal:21428/insert/opentelemetry/v1/traces
VictoriaTraces is still on a v0.x release line — read the release
notes before bumping the version in grafana/.env.
Configure these env vars in each service's .env to ship OTLP traces:
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://host.docker.internal:21428/insert/opentelemetry/v1/traces
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
| Service | Native OTLP support | service.name in traces |
|---|---|---|
| LiteLLM | Yes (built-in) | litellm |
| Langfuse | Yes (worker) | langfuse |
| n8n | Yes (OTEL env vars) | n8n |
| Windmill | Yes (OTEL env vars) | windmill |
source ./env.sh
BASE="$YAI_VTRACES_JAEGER_URL"
# List all services emitting traces
curl -s "$BASE/api/services" | jq -r '.data[]'
# Operations for a service
curl -s "$BASE/api/services/litellm/operations" | jq -r '.data[]'
# Recent traces for a service
curl -sG "$BASE/api/traces" \
--data-urlencode "service=litellm" \
--data-urlencode "limit=20" \
| jq '.data[] | {traceID, duration, spans: (.spans | length)}'
# One trace by ID
curl -s "$BASE/api/traces/<traceID>" | jq
OTEL_EXPORTER_OTLP_PROTOCOL=grpc.jaeger, pointed at YAI_VTRACES_JAEGER_URL.http://host.docker.internal:21428/insert/opentelemetry/v1/traces (not localhost from inside a container). Verify with curl -s http://localhost:21428/api/v2/services.trace_id via OTLP when success_callback: ["langfuse"] is set. The Langfuse trace ID and the vtraces span ID share a root — search by the same trace_id in both systems.agent-browser CLI — headless Chromium for AI agents. Snapshot-and-ref workflow, core commands, and yai service interaction patterns. Auto-load when asked to open a browser, navigate a URL, click, fill, screenshot, or interact with any yai web UI (Grafana, n8n, Windmill, Langfuse, MinIO, etc.).
Browserless headless Chromium service on the yai stack — REST endpoints (screenshot, PDF, scrape, function), WebSocket CDP/Puppeteer/Playwright patterns, token auth, sizing. Auto-load on Browserless, headless browser, Puppeteer, Playwright, CDP, screenshot, PDF, scrape-script questions.
Generate clean architecture / flow diagrams as PNG+SVG for the yai stack. Hand-laid-out Python→SVG→PNG pipeline (no Mermaid auto-layout). Auto-load when asked to create, update, or render an architecture diagram, flow chart, system diagram, or "draw the stack".
Firecrawl web crawling & scraping API on the yai stack — scrape, crawl, extract endpoints, job status, concurrency knobs, proxy config. Auto-load on Firecrawl, web scrape, crawl, extract, markdown, web content questions.
Grafana on the yai stack — datasource UIDs, file provisioning (not TF), dashboard conventions, scrape targets page, Grafana plugin setup. Auto-load on Grafana, dashboard, datasource, DS_*, panel, templating variable, provisioning questions.
How to control every yai web UI — login recipes, navigation patterns, and common actions for Grafana, Langfuse, MinIO, n8n, Windmill, LiteLLM, Qdrant, and Traefik. Auto-load when asked to log in, navigate, click, or perform any action in a yai service UI.