DX App Experience Analytics does not capture user ID for some transactions.

Products

• CA App Experience Analytics

Issue/Introduction

For session <session id>, DX App Experience Analytics captured the Customer ID, <id>. The same user executed another transaction, with session ID <session id>, using the browser in both sessions, but DX App Experience Analytics did not capture the user's Customer ID. This makes it difficult to track issues by user.

Resolution

The LOGIN Business Transaction is created manually, from a customer javascript, which is called in Windows load event listener for the login page. But the load event is only triggered after all dependency resources are loaded. 

So possibly sometimes if there were problem loading some dependency resource the Windows load event was never triggered or came too late,  then the "LOGIN" BT won't be created, resulting in:

- APM side LOGIN traces will be missing, therefore LOGIN Vertex will be missing, so in OI Performance UI no LOGIN Entity and its associated Metrics.

- AXA side: Customer Id set during login will also be missing.

Eng explained the whole process and theory and asked for someone who owns the customer JavaScript (inc_fuc_axa.js) to help and confirm. 

Bottom line is -- if the BA Ext API to create the BT was not called, there isn't much we can do from APM/AXA

For next step, Customer will find a more reliable entry point to create the "LOGIN" BT.