trace-query

Query BytedTrace distributed tracing data by trace ID across multiple regions.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill trace-query-yuezhen-huang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace-query
Source: https://github.com/yuezhen-huang/my-bytedance-skillhub/tree/main/trace-query
Command: npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill trace-query-yuezhen-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging distributed systems, engineers need to retrieve and inspect end-to-end request traces, but trace data is scattered across regional BytedTrace deployments. This Skill queries distributed tracing data by trace_id across multiple regions without manually switching between regional endpoints. ## Core Features & Use Cases - Cross-Region Trace Lookup: Query a single trace_id across Singapore, US-East, EU-TTP2, US-EastRed, US-TTP, US-TTP2, and China-North regions in one call. - Flexible Time Windows: Specify relative time ranges (e.g., 5m, 1h, 24h) or explicit Unix start/end timestamps to locate traces. - Structured Trace Output: Returns root span info, transactions with spans and tags, summary statistics, and highlighted errors for rapid diagnosis. - Use Case: A user reports a failed checkout request and provides a trace_id. Query the trace across US-TTP and Singapore-Central with a 1-hour window to find the failing span and its error tags. ## Quick Start Ask the agent to query trace 5ae9863e-1065-4a6b-276f-0dab00000000 in the Singapore-Central region with a 10-minute time range.

Frequently Asked Questions about trace-query

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

FAQPage Schema
How do I query a distributed trace by trace ID?

Provide the trace_id parameter with the trace identifier, for example trace_id=5ae9863e-1065-4a6b-276f-0dab00000000. Optionally add vregion and time_range parameters to narrow the search scope.

How do I search a trace across multiple regions at once?

Pass a comma-separated list to the vregion parameter, such as vregion=Singapore-Central,US-East,China-North. The query fans out to each regional BytedTrace endpoint and aggregates the results.

Which regions does BytedTrace trace query support?

Supported regions are Singapore-Central, US-East, EU-TTP2, US-EastRed, US-TTP, US-TTP2, and China-North. Each region maps to its own BytedTrace base URI, and Singapore-Central is the default when vregion is omitted.

Can I specify a custom time range for trace lookup?

Yes, use time_range with relative values like 5m, 1h, or 24h, or provide explicit start and end Unix timestamps. The default window is the last 10 minutes.

Why does my trace query return no data?

The trace may have expired outside the scanned time range, been sampled out, or reside in a different region than queried. Widen the time_range, add more vregion values, and confirm the trace_id is correct.