Injecting special headers into an application payload is disturbing application functionality. How do I resolve this?
Disable the exit call correlation based on the exit call that is being sent to the payload. There are two ways to disable exit call correlation in order to stop writing correlation headers to the payload.
Refer to the following screenshot for disabling exit call correlation for IBM MQ and other backends.
I don’t see some of the async threads tracked on environments where Camel, Mule, JBoss ESB, Tibcow, or Scala are used. Please help!
First, stop the Agent.
Navigate to the app-agent-config.xml file located under agent-install-dir>/conf folder
Add a list of async environment names separated by commas to the config file. This will enable async transaction detection for supported environments, which include all of the above.
The snippet will look like this:
<!-- Add comma-separated list of async environment names.These will be used to enable async transaction detectionfor supported environments.Current supported async environments: mule,camel,jbossesb,tibcobw,scala --> <!--property name="enable-async-correlation-for" value="mule,camel,jbossesb,tibcobw,scala"/ -->
Then add the following code above or below the previous snippet:
Option 2 - Disable JMS correlation on an upstream tier, so that the Agent will not be allowed to write any special headers to the JMS payload. This option will not allow the user to see the correlation between producer and consumer.