App Experience Browser Agent, Correlation ID and PHP-Probe with APM integration

Products

• DX APM SaaS
• DX Application Performance Management
• CA Application Experience Analytics SaaS (AXA)

Issue/Introduction

When configuring Web applications to be monitored End to End, the correlation ID makes sure that the path of the user can be followed from the click of a URL through to the back-end Database.
The Browser Agent snippet can be installed through various methods. By adding it straight to the code of the Web-Page, or by adding it through automatic injection through a APM agent upstream.
The correlation ID is shown by the marked icon in the session view on DX App Experience Analytics

Environment

DX App Experience Analytics, DX APM Agent/php-probe

Cause

If the Browser Agent snippet is installed manually into the web-application code, the injected correlation ID is not linked to the agent, hence correlation will not be possible and the link to the experience view in APM is missing.
The Correlation ID is generated by the php-probe, hence has to be added by it.

Resolution

The Browser Agent snippet has to be injected into the response by the APM Agent/probe (here php-probe) so that a correlation ID actually is valid. 

This is done in the PHP-Probe - file: wily_php_agent.ini

by enabling the 

wily_php_agent.enable.browseragent.snippet.autoInjection=1

And adding the BAjs snippet:

wily_php_agent.browseragent.autoInjection.snippetString='<script type="text/javascript" id="idstring" src="https://dxc.dxi-eu1.saas.broadcom.com/api/1/urn:ca:tenantId:<tenantID>/urn:ca:appId:AppNAme/bajs?agent=browser" data-profileUrl="https://dxc.dxi-eu1.saas.broadcom.com/api/1/urn:ca:tenantId:<tenantID>/urn:ca:appId:AppNAme/profile?agent=browser" data-tenantID="<tenantID>" data-appID="AppNAme" data-appVersion="1.0" data-use-axa-appname="true" data-appKey="<AppKey" async ></script>'

Additional Information

 

Note that this probably also applies to the JAVA agents.