Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

acceptDistributedTracePayload - but no distributed traces

distributedtracing

#1

We implemented distributed traces:

  1. createDistributedTracePayload in tomcat 1 app 1
  2. transport payload via header to another service
  3. receive payload in another service tomcat 2 app 2
  4. acceptDistributedTracePayload

Sometimes we see distributed traces, but mostly not.

How do we debug the agent? Is there any indication that agent actually accepted the payload and matched it to another transaction?


#2

Hi @andrey.kan -

There are a couple of things you could look into with debugging missing distributed traces - For instance, ensure you have a valid Java agent that supports distributed tracing on app1 and app2. Next, kindly review our online documentation to help with troubleshooting called services with the Java agent.

Excerpt from our online documentation :

One way to tell that a transaction is not in progress: when createDistributedTracePayload() is called, an empty string is returned. To create a transaction, see Java agent transaction-related APIs.

In addition, we have some troubleshooting steps on our online documentation linked below, that can be used to track missing trace data:
https://docs.newrelic.com/docs/apm/distributed-tracing/troubleshooting/troubleshooting-missing-trace-data

I hope the aforementioned documentation is helpful.