New Relic APM's cross application tracing lets you link transactions between your APM-monitored applications.
What is cross application tracing?
Instead of using cross application tracing, we recommend our distributed tracing features. Distributed tracing is an improvement on the cross application tracing feature and is recommended for large, distributed systems.
New Relic APM's cross application traces link transactions between APM apps in your service-oriented architecture (SOA). This is useful, for example, to identify performance problems between your own application (the "calling" app) and any internal or external services (the "called" app), such as traffic to internal services.
This helps you to:
- Spot bottlenecks in your cross application call flows.
- Understand from end to end how specific transactions are used by other applications and services.
- Diagnose problems faster and enhance collaboration across teams.
Cross application tracing relies on three HTTP headers in order to exchange information between the calling and called applications.
- The first two (
X-NewRelic-Transaction) appear as HTTP request headers in outgoing requests sent by an instrumented application.
- The remaining header (
X-NewRelic-App-Data) is inserted into the HTTP response if the called application belongs to the same New Relic account as the calling application.
New Relic obfuscates all of these headers using an obfuscation scheme identical to what is used for New Relic Browser's configuration for page load timing (sometimes referred to as real user monitoring or RUM) but with a different key.
(in request header)
|Contains the account ID and application ID of the application making the call|
(in request header)
|Contains information about an individual transaction created by the call (a GUID unique to the calling transaction, along with information about upstream calls that spawned the transaction)|
(in the response if applicable)
Contains information about the called application, including: