Browser Agent and Java Agent Traces are not correlated
search cancel

Browser Agent and Java Agent Traces are not correlated


Article ID: 91903


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE


Browser Agent and Java Agent Traces are not correlated - Checklist


Release: CEMUGD00200-10.5-Introscope to CA Application-Performance Management-Upgrade Mai


1.- Correlation depends on the below Agent properties, make sure they have been enabled and configured in the IntroscopeAgent.profile:

Important: Verify that the pages you want monitor are not being excluded by includeURLsRegex.
Changes to the above properties takes effect immediately
2.- In your browser press F12, go to the “Network tab”, open the page you would like to inspect, then click  “Cookies” tabs.

Verify that x-apm-brtm-response-bt-page-<you-app-url> includes the CorBrowsGUID or value. 


If you can't find the cookie, then problem is inserting the cookie, make sure Cookies are enabled in the browser, see Browser Agent Prerequisites:


If you find the cookie, switch from the “Network” to the “Console” tab, check if the javascript can read the cookie, if you see the warning message like below, then problem is in reading the cookie:

a) cookie has already expired : increase introscope.agent.browseragent.response.decoration.cookie.expirationTime=3 to a higher number, and try again

b) cookie can't read because the cookie name. This requires debugging in the JavaScript side.

    Open the IntroscopeAgent.profile, set,logfile, reproduce the issue and contact CA Support.



3. Verify that the Introscope trace passed the trace session.

Go to the <DxC-hostname> | DxC Agent | Logstash-APM-Plugin | Business Segment, click “Traces” tab, review the timestamp of the Traces for the application you are inspecting
Go to the <App-hostname> | <Process> | <agent> | Frontends , click Traces tab, look for Introscope traces that appear at the same or approximate time
Below is an example illustrating BrowserAgent and Introscope correlation, you can see the 2 threads containing:
a) Browser Agent timing metrics gathered by DxC reported as “Business Segment” data
b) Normal trace gathered by the agent instrumentation.
See how  the “Cross Process Data” matches in both threads. You can also jump to Business Segment in DxC in case you need to investigate further the issue from the DxC side

User-added image