• EnglishEspañol日本語한국어Português
  • Log inStart now

Troubleshoot cross application tracing

Here are troubleshooting tips when using cross application traces. Note that this feature is not the same as distributed tracing, which is preferred over cross application tracing.

Agent versions and protocols

Make sure you meet these requirements for your agent's version, protocols, interfaces, or message queue libraries. If you are using a protocol that is not listed here, you will not see a connection between your applications.

Agent version


Go 1.11 or higher


Java 3.9.0 or higher

HTTP, HTTPs, JMS 1.1, RabbitMQ

The Java agent also supports several message queue libraries, including those that use the JMS 1.1 interface.

.NET 4.2 or higher

HTTP, and supported .NET messaging systems

Node.js 2.0.0 or higher


PHP 4.19.0 or higher

HTTP, HTTPS, and supported PHP message queuing systems

Python or higher

HTTP, HTTPS, and supported Python message queuing systems

Ruby 4.3.0 or higher


Config file requirements

In general, New Relic's cross application tracing feature is enabled by default. Requirements to change your configuration file vary, depending on your New Relic agent:

High throughput apps

Cross application traces rely on transaction events to associate related transactions. If you have a high throughput application, your agent may reach the maximum number of events that it can record in a minute and will fall back to sampling events. If a transaction’s events are sampled, you may see an incomplete cross application trace, including sometimes only the transactions that you are focused on.

If your application has high throughput, some cross application traces will appear incomplete, sometimes with no links. Try viewing a different transaction trace. To reduce or eliminate sampling, you can also adjust the number of transaction events stored in your agent configuration.

High throughput apps

Troubleshooting tips


In the transaction_events section, adjust the setting for max_samples_stored.


Adjust the setting for analytics_events.max_samples_stored.


If you expect to see a cross application trace link but it consistently does not appear, there may be a proxy or broker between your application’s communication. Cross application tracing relies on HTTP headers and JMS properties being passed from one application to other. HTTP proxies and message brokers sometimes strip those headers.

Multi-threaded processing (Java)

If one or more of your Java applications uses an async or "reactive" programming model, a transaction's activity may span across multiple threads. New Relic supports the Play framework and Servlet Async but not all async frameworks. For unsupported frameworks, activity on other threads is not reported as part of the transaction. Calls to other applications will not be traced.

Multiple accounts

Currently cross application traces do not cross New Relic accounts. If you have multiple New Relic accounts (including child accounts), you will only see traces for applications within one account.

Our distributed tracing feature does cross account boundaries.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.