1. Docs
2. API
3. Direct Links to Traces

Direct Links to Traces

It can be useful to launch directly into a trace waterfall 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.

Construct a URL with this template:

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

In this URL:

• team and dataset are the usual fields seen in Honeycomb URLs
• trace_id specifies the (URL-encoded, if necessary) unique trace id for that trace.
• trace_start_ts and trace_end_ts describe roughly the time range to look for the trace. They are specified in UNIX-style integer timestamps.

The query engine will look for traces with this trace_id in the specified time range. If no time range is specified, it will look from the current time, to two hours ago.

If only a trace_start is provided, and no end, 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.