Access to this feature depends on your subscription level.
Agent versions and protocols
In order for a transaction to appear as a color-coded node in the transaction map or trace map, it must be monitored by the appropriate version of the New Relic agent. 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.
|Go 1.11 or higher||HTTP, HTTPS|
|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||HTTP, HTTPS, RabbitMQ|
|PHP 4.19.0 or higher||HTTP, HTTPS, and supported PHP message queuing systems|
|Python 22.214.171.124 or higher||HTTP, HTTPS, and supported Python message queuing systems|
|Ruby 4.3.0 or higher||HTTP, HTTPS, RabbitMQ|
Config file requirements
In general, New Relic's original cross application tracing feature is enabled by default. Requirements to change your configuration file vary, depending on your New Relic agent:
- Go (not supported)
- Node.js (no specific config file settings needed for Node.js)
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|
|Java||From the transaction_events stanza, adjust the setting for
|Ruby||Adjust the setting for
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.
Currently cross application traces do not cross New Relic accounts. If you have multiple New Relic accounts (including sub-accounts), you will only see traces for applications within one account.