The trace view is designed to make navigating, investigating, and sharing data about an individual end-to-end transaction (i.e. a "trace") both easy and intuitive. Whenever a trace is viewed in LightStep, it is persisted forever so that it can be bookmarked, shared, and reviewed by your team at any point in the future.
The trace mini-map shows a condensed view of the overview trace, allowing you to quickly navigate to different parts of large, complex traces. The different services within the system are displayed in different colors to give a sense of the overall service interactions.
The trace mini-map can toggle between two modes: an “icicle graph” intended to give a sense of the overall shape of the trace and a single-line condensed view designed to take up minimal screen space.
The expanded mini-map
The collapsed mini-map
The main view of the trace contains a wealth of information about the individual spans within the trace:
LightStep automatically runs a heuristic to determine the critical path of a given trace. The critical path is highlighted in yellow to help identify bottlenecks in the overall transactions.
The trace critical path
Spans with errors
When spans have a parent id that wasn't found to be a span id in any of the Satellites, they are highlighted with a dashed red box. This can be a Satellite related span drop (for example, your Satellite pool is not auto-scaling to keep up with traffic) or client-side span drop (for example, your application crashed or never called span.flush() )
Span with missing span errors.
The side panel contains information about the currently selected span in the trace. This includes information about the span itself, its tags, and the logs. This information is a direct reflection of the OpenTracing span information.
Log payloads are displayed inline with the log information. Payloads are a powerful feature for capturing detailed information for transactions of interest.