Share a Trace | Honeycomb
  1. Docs
  2. Investigate
  3. Share a Trace

Share a Trace

It can be useful to launch directly into a trace waterfall display from a Trace ID from third-party services. For example, you might wire an error reporting tool to launch directly into a trace in Honeycomb.

Note
Embedding Trace waterfalls (or other Honeycomb pages) within an iframe is not supported.

Construct a URL with this template:

https://ui.honeycomb.io/<team>/environments/<environment>/datasets/<dataset>/trace?trace_id=<traceId>
  &span=<spanId>
  &trace_start_ts=<ts>
  &trace_end_ts=<ts>

The query engine looks for traces with this trace_id in the specified time range. In this URL:

  • team, environment, and dataset are the named respective fields as seen in Honeycomb URLs

    Note

    A direct link works with /datasets/<dataset>/ omitted from the URL template:

    https://ui.honeycomb.io/<team>/environments/<environment>/trace?trace_id=<traceId>
  &span=<spanId>
  &trace_start_ts=<ts>
  &trace_end_ts=<ts>

  • trace_id specifies the (URL-encoded, if necessary) unique trace ID for that trace

  • span specifies the unique ID of the span to jump to within the trace. If no span with a matching span ID is found, the link defaults to the root span of the trace.

  • trace_start_ts and trace_end_ts describe roughly the time range to look for the trace. They are specified as UNIX/Epoch-style integer timestamps. These timestamps are measured in seconds, in Coordinated Universal Time(UTC).

If no time range is specified, it will look from the current time to two hours ago.

Example  

https://ui.honeycomb.io/team/environments/environment/datasets/dataset/trace?trace_id=d82cb2fcf355dc40789106f673400d06
  &span=32e459181a2c6098
  &trace_start_ts=1704067200
  &trace_end_ts=1704153600

Considerations 

If only a trace_start_ts is provided with no trace_end_ts value, then the query engine will look for traces within ten minutes of the starting time of the start.

Note that the trace waterfall may miss some spans if the query range is too narrow. On the other hand, the query engine may take longer to look across broader time periods.

Note

For Datasets within Honeycomb Classic, construct the URLs with this template:

http://ui.honeycomb.io/<team>/datasets/<dataset>/trace?trace_id=<traceId>
  &span=<spanId>
  &trace_start_ts=<ts>
  &trace_end_ts=<ts>
On this page: