Docs » Manage services, spans, and traces in Splunk APM » Explore your traces using Trace Analyzer

Explore your traces using Trace Analyzer 🔗

Trace Analyzer lets you search traces generated by your application and identify patterns in the full-fidelity trace data without prior knowledge of which tags are relevant.

Trace Analyzer is available to all Splunk Observability Cloud Splunk APM users.

Examples of questions that Trace Analyzer helps you answer include:

  • How many traces and traces with errors exist for a given combination of service, environment, and tags?

  • For a given issue, which customers experience the highest error rate?

  • How to locate error spikes in my trace data?

When to use Trace Analyzer 🔗

Splunk Observability Cloud provides several tools for exploring application monitoring data. Trace Analyzer is suited to scenarios where you have high-cardinality, high-granularity searches and explorations to research unknown or new issues. See Guidelines for working with low and high cardinality data.

The following table presents what each APM tool is best suited for:

APM tool

Scenario

Analysis level

Cardinality

Documentation

Trace Analyzer

Identify patterns for unindexed tags

Trace-level analysis

High cardinality

Tag Spotlight and service map

Surface trends for indexed tags

Service-level analysis

Medium cardinality

Analyze service performance with Tag Spotlight

Monitoring MetricSets

Get alerts on service degradation

Workflow and service-level analysis

Low cardinality

Generate a Monitoring MetricSet with a custom dimension

Explore your trace data 🔗

To open Trace Analyzer, select Traces in Splunk APM and select Switch to Trace Analyzer. To switch back to the classic traces view, select Switch to Classic View. See Explore your traces using Trace Search for more info about the classic traces view.

To explore your trace data, use the following controls, which are numbered as callouts in the image. Additional details for each callout follow the image:

Elements of the Trace Analyzer user interface
  1. Use the filter bar to refine the traces by time range, environment, workflow, services, and tags.

  2. Use the minimum and maximum trace duration to refine the traces that are included by their duration.

  3. Use the sample ratio to select all traces or 10% of traces.

  4. Use the Errors Only switch to show only traces with errors.

  5. Use the search to look up a trace by its ID.

  6. Use the real-time chart to view the count of total traces with errors.

  7. Use the table of traces to view trace details or group metrics based on a tag.

Trace Analyzer searches all currently retained traces; see Data retention in Application Performance Monitoring (APM) to learn more about the default trace retention period.

Explore trace and error counts 🔗

Trace Analyzer shows total traces and traces with errors in a stacked bars chart. Select and drag over the bars in the chart to select a specific period within the available time frame. Select Filter to selection to update the time range filter.

Selection of a specific time frame

Group by tag 🔗

You can group all available traces by a single tag or attribute. For example, you can group all traces from your service by database table, host name, or HTTP status code.

Tag selection menu of Trace Analyzer

The resulting Group Metrics tab shows a breakdown of the top 100 values for the selected tag, ranked by the number of errors.

Metric table in Trace analyzer

You can order both tables by the number of matching traces.

Trace Analyzer trace limits 🔗

Trace Analyzer can search a maximum of 6 hours of data.

Within the Trace Analyzer interface, there are three different display limits. The Trace Analyzer chart (1) and the Group Metrics (2) tab display up to 6 hours of traces. The list of traces displayed on the Traces tab (3) has a limit of 1,000 traces. For the Traces tab, Trace Analyzer searches for traces at the end of the time window you select. When 1,000 traces are matched or the six-hour search window is reached, the list stops populating.

Trace limit in trace list

Learn more 🔗

See the following links for more information on Trace Analyzer: