1.- Traces correlation depends on the below Agent property, make sure it has been enabled in the IntroscopeAgent.profile:
This is a hot property.
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 in inserting the cookie, make sure Cookies are enabled in the browser, see Browser Agent Prerequisites:
a) cookie has already expired : increase introscope.agent.browseragent.responseCookie.expirationTime =3 to some high number, and try again
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, locate the Traces for the application you are analyzing
Go to the <App-hostname> | <Process> | <agent> | Frontends , click Traces tab, locate the relevant Introscope traces.
Below is an example illustrating BrowserAgent and Introscope correlation, you can see 2 threads containing:
a) Browser Agent timing metrics gathered by DxC reported as “Business Segment” data
b) Normal trace gathered by the agent instrumentation.
Notice how “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 node