Menü
Distributed traces - search OTel spans, follow traces, service dependency map.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
AI Teammate - manage connectors (PagerDuty, Slack, GitHub, ...), update teammates (agents) and view teammate activity.
Pipelines - fleet management, config changes, version history, deployments and live capture.
Dashboards - create, update, inspect and validate metric dashboards from the CLI.
Cross-signal incident investigation workflow - from alert to root cause using events, patterns, logs, metrics, traces and pipeline history.
Metrics - discover metric names and run aggregation queries (timeseries and tables).
Monitors - create, manage, snooze and resolve Edge Delta monitors and alerts.
| name | ed-traces |
| description | Distributed traces - search OTel spans, follow traces, service dependency map. |
| metadata | {"version":"1.0.0","author":"edgedelta","repository":"https://github.com/edgedelta/agent-skills","tags":"edgedelta,traces,apm,spans,otel,service-map","alwaysApply":"false"} |
Search distributed traces (OpenTelemetry spans) and the service map.
The edx CLI must be installed and authenticated. See the ed-edx skill.
field:"value" CQL syntax. Full-text search is NOT
supported and will error.service.name, status.code, span.kind, trace_id,
ed.tag. Discover more: edx facets keys --scope trace.status.code holds the HTTP status code (200, 404, 500, ...), not a
span-status word. Query server errors as status.code:"500" (or another
5xx); status.code:"ERROR" matches nothing. Enumerate live values with
edx facets options --scope trace --facet status.code.# Server-error (5xx) spans, last hour
edx traces search -q 'status.code:"500"' --lookback 1h
# Server-side spans of one service with full trace context
edx traces search -q 'service.name:"checkout" AND span.kind:"server"' --include-children
# Everything in one trace
edx traces search -q 'trace_id:"<id>"' --include-children
--include-children pulls child spans of matches so you can see where time
went inside the request.
The service dependency graph built from traces - which services call which, with health/latency context:
edx service-map --lookback 1h
Use it early in an investigation to find blast radius: an erroring service's upstream callers are affected, its downstream dependencies are suspects.
edx traces search -q 'status.code:"500"' - find failing spans.trace_id, fetch the whole trace with --include-children.edx logs search -q 'service.name:"<svc>" AND severity_text:"ERROR"'.field:"value".edx facets options --scope trace --facet service.name.--lookback; traces may be sampled.