After selecting a trace from the trace list, you'll be directed to the trace details page in the UI. Use trace details to understand the flow of operations that make up a distributed trace, and adjust the view to find the information most important to you.
Select a trace from the list of traces to see details about it.
Check out ways to display your traces' spans:
The timeline view is a high-density view of all the spans in the trace. This view allows you to quickly scroll through the entire trace and see how latency and errors propagate through the trace and across entity boundaries. You can select spans from this view to see span details in the waterfall view below it.
The latency view shows you how much latency is contributed by each entity in the trace, as well as the number of error spans per entity. The latency contributed by an entity is the wall-clock time that it had one or more processes running but was not making any external or database calls. Here are two examples:
If an entity has a process lasting 500ms, but 400ms of that time it's making an external call, it's shown as contributing 100ms of latency to the trace.
If an entity has three processes running in parallel for one second, and none of them made external calls, it's shown as contributing one second of latency to the trace.
The waterfall view in the bottom section of the page displays a detailed flow of all the operations that make up the distributed trace. This allows you to see the exact context from which latency and errors arise.
The waterfall view has a number of controls to make it easier to find spans that you care about:
Expand all/Collapse all: Use this option to toggle between showing every span (including in-process spans) and showing collapsed spans.
Standard/Manual: In standard mode, you get a semi-expanded view that includes the first span in each process. In manual mode, you only see what you expand.
- Both Standard and Manual are overridden by Expand all, which displays all spans.
- If you're in standard or manual mode, and you click Collapse all, the waterfall is reset to the default for the mode you're using.
Focus on: If your span has errors or anomalies, you'll see checkboxes for each of these types. If you check these boxes, your waterfall view will collapse all other types of spans and only show color-coded error or anomalous spans. This is a quick way to find problematic spans.
Maximize: This allows you to see more spans on the screen by expanding the waterfall and hiding the entity map.
The UI indicates span properties with these icons:
This icon represents a span that's a service's entry point.
This icon represents an in-process span, which is a span that takes place within a process (as opposed to a cross-process span). Examples: middleware instrumentation, user-created spans.
This icon represents a span call to a datastore.
This icon represents category representing a call to an external service made via HTTP.
This icon represents a browser application span.
This icon represents a span from a Lambda function.
Some spans will have additional indicators:
Type of connection
Solid lines indicate a direct parent-child relationship; in other words, one process or function directly calling another. A dotted line indicates a non-direct relationship. For more on relationships between spans, see Trace structure.
A span with an error. See How to understand span errors.
This icon represents the detection of an anomalous span.
Some spans may be "orphaned," or separated, from the trace. These spans will appear at the bottom of the trace. For more details, see Fragmented traces.
Multiple app names
When beside a span name, this represents an entity that has had multiple app names set. Select this to see all app names it reports to. To search trace data by alternate app names, use the
Client/server time difference
If a span's duration indicator is not completely colored in (like in this example), it means that there is a time discrepancy between the server-side duration and the client-side duration for that activity. For details on this, see Client/server time difference.
When you select a span, a pane opens up with span details. These details can be helpful for troubleshooting performance issues. This page has three tabs:
- Performance: You’ll see charts showing the average duration and throughput for that span operation, as well as how the performance of this specific span compares to the average.
- Attributes: You can learn more about attributes from our data dictionary.
- Details: You can view details, such as the span's full name and data source.
What a span displays is based on its span type. For example, the datastore span's details will include the database query. For more on the trace structure and how span properties are determined, see Trace structure.
If you'd like to learn more about
- Explore your span data using the query builder.
- To see the default attributes attached to span data, use the data dictionary.
- Check out these example queries for help with NRQL queries using these attributes.
If you are using our logs in context feature, you can see any logs that are linked to your traces:
- Go to the trace details page by clicking on a trace.
- In the upper-left corner of the span details page, click the Logs tab.
- For details related to an individual log message, click directly on the message.