Link directly to any trace in Honeycomb for faster, context-rich debugging.
Direct trace links let you open specific traces in Honeycomb from external tools like error trackers, alert systems, and incident response platforms. These links are especially helpful when connecting Honeycomb to third-party tools, so you can jump straight from a notification or alert to the relevant trace for investigation.
A direct trace link is a Honeycomb URL that opens a trace waterfall view using a Trace ID. When someone opens a direct trace link, Honeycomb displays the trace waterfall view for that specific trace.
iframe isn’t supported.Construct a direct trace link by combining your Honeycomb region, trace context, and time range into a URL.
To open a trace directly, construct a URL in this format:
https://<subdomain>.honeycomb.io/<team>/environments/<environment>/datasets/<dataset>/trace?trace_id=<traceId>
&span=<spanId>
&trace_start_ts=<ts>
&trace_end_ts=<ts>
When opened, Honeycomb searches for traces matching the given trace_id within the specified time range.
If you are linking to a dataset in Honeycomb Classic, use this URL format instead:
http://<subdomain>.honeycomb.io/<team>/datasets/<dataset>/trace?trace_id=<traceId>
&span=<spanId>
&trace_start_ts=<ts>
&trace_end_ts=<ts>
Each part of the URL identifies the trace and its context:
subdomain: Subdomain of the Honeycomb UI instance for your region:
uiui-eu1team: Slug for the Team in Honeycomb.
This short, URL-friendly string uniquely identifies your Team and appears in Honeycomb URLs.
environment: Slug for the Environment in Honeycomb.
This short, URL-friendly string uniquely identifies your Environment and appears in Honeycomb URLs.
dataset: Slug for the Dataset in Honeycomb.
This short, URL-friendly string uniquely identifies your Dataset and appears in Honeycomb URLs.
You can omit /datasets/<dataset>/ from the URL and the link will still work:
https://<subdomain>.honeycomb.io/<team>/environments/<environment>/trace?trace_id=<traceId>
&span=<spanId>
&trace_start_ts=<ts>
&trace_end_ts=<ts>
trace_id: Unique identifier of the trace. URL-encode if necessary.
span: Unique identifier of the span to jump to within the trace.
If no matching span is found, the link opens to the trace’s root span.
trace_start_ts: Start time for the time range to search.
Specified as a UNIX/Epoch-style integer timestamp in seconds (UTC).
If only a start time is provided, Honeycomb searches for traces within ten minutes after this timestamp.trace_end_ts : End time for the time range to search.
Specified as a UNIX/Epoch-style integer timestamp in seconds (UTC).This example shows a complete direct trace link for the US region, including a span and a defined time range:
https://ui.honeycomb.io/my-team/environments/my-env/datasets/my-dataset/trace?trace_id=d82cb2fcf355dc40789106f673400d06
&span=32e459181a2c6098
&trace_start_ts=1704067200
&trace_end_ts=1704153600
Follow these tips to build direct trace links that load efficiently and return complete, reliable results:
trace_start_ts and trace_end_ts helps Honeycomb locate the trace efficiently.trace_start_ts, Honeycomb automatically searches for traces within ten minutes after that time.Keep these points in mind to ensure your direct trace links work as expected:
iframe.