AXA sessions with the same application name.
search cancel

AXA sessions with the same application name.

book

Article ID: 207696

calendar_today

Updated On:

Products

CA Application Experience Analytics SaaS (AXA)

Issue/Introduction

We have an App deployed in 2 different environments. UAT and PROD, but both reporting to same SaaS tenant.

- On AXA side, we have 2 different Apps defined for the 2 env., so the Browser Agents are configured to report separately, to either UAT or PROD.

- But once click into isolation view for a Network Event from one env., i.e. UAT, nodes from both environment show up, as we simply filter based on the App/BT name, which is same for both environments

- So basically we can't differentiate the 2 env. from APM side for this Use Case.

Environment

Release : SAAS

Component : CA APP EXPERIENCE ANALYTICS SAAS

Resolution

This is working by design. It is best practice to include the environment as well as the application in the application name field. . Such as SprocketApp_Production and SprocketApp_UAT.