Additional distributed tracing features in New Relic One

New Relic One gives you search and filter features in addition to the standard distributed tracing features. This document explains:

  • How to find distributed traces in New Relic One.
  • How to filter your traces using the query bar and histograms.
  • Cross-account security.

Find distributed traces in New Relic One

There are two ways to view your distributed tracing data in New Relic One:

  • Global view: Go to > Distributed tracing. You'll see a global view of traces from across all available services. The details available may be limited based on the New Relic accounts you have access to.
  • Service-specific view: Go to > Entity explorer > (select a service). If distributed tracing data is available for that service, you'll see a Distributed tracing tab that contains traces associated with that service.

Use these tools to find and filter traces:

Filter traces with queries

The Find traces query bar is located at the top of all trace lists in New Relic One. You can either start typing in the query bar or use the dropdown to create a compound query.

Query returns are based on span attributes, not on trace attributes. You define spans that have certain criteria, and it displays traces that contain those spans.

Let's look at an example query. See the caption for an explanation of how this query works.

new-relic-one-distributed-tracing-query-example-1.png > Distributed tracing: This query will find traces that 1) pass through both WebPortal and Inventory Service applications, 2) have an Inventory Service datastore call that takes longer than 500 ms, and 3) contain an error in any span.

Here's another example query:

Find traces that match a partial email address string
New Relic One distributed tracing - query example 2 > Distributed tracing: This query will find traces that 1) contain spans that pass through the WebPortal application and where an error occurred on any span in the WebPortal application, and 2) contain spans where the customer_user_email attribute contains a value ending with "" anywhere in the trace.

Additional details about query functionality:

  • It works similarly to NRQL (our query language). The main exceptions:
    • String values don't require quote marks (for example, you can use either appName = MyApp or appName = 'MyApp')
    • The like operator doesn’t require % (for example, you can use either appName like product or appName like %product%).
  • Some queries that return a large number of results may return false positives. The trace list limits these incorrect results to 10% of the returned results. False positives may also result in histogram chart results that are not displayed in the trace list.

Use histograms to filter traces

Trace histogram charts are available only on the global distributed tracing page.

The histogram charts give you a quick understanding of trace distribution for important values, like duration. You can use the sliders under the charts to control what traces are displayed. For example, you can drag the Trace duration chart slider to show only traces over 500 ms, as shown in the histogram example below.

New Relic One distributed tracing - histogram

Note: Some queries that produce many results may result in false positives showing up in histograms. This could manifest as histograms showing trace results that are not in the trace list.

Other features

This document explains only New Relic One-specific distributed tracing features. For standard features, see Distributed tracing UI.

Cross-account security

For New Relic accounts that are associated with one another (for example, in the same organization), our distributed tracing feature provides cross-account information. For data security purposes, if you don't have access to the accounts that monitor services in a trace, we will obfuscate details for those services.

For more on this, see Cross-account obfuscation.

For more help

Recommendations for learning more: