Isolation view feature explanation

Products

• CA Application Experience Analytics SaaS (AXA)

Issue/Introduction

How does the isolation view from AXA work? I am not seeing all transactions with the Isolation view icon available. Some Isolation view icons do not lead us the the right topology.

 

 

Environment

DX O2 On premise 24.2 HF5

Resolution

In order to have the Isolation view icon, the transactions must follow the below rules:

• In order to click and have the map of the isolation view, the URL must have a backend call, otherwise, it will not work.
• Not all URLs that is being mapped must have an isolation view.
• The Backend of the URL is assigned to the URL to the Business transaction.
• By creating a filter to list all URl that has Businness transaction the customer can drill down using an isolation view.

Not all URLs in AXA can be mapped in the topology:

AXA will record all visible transactions, however, the topology(Isolation view) will be available if this URL has a backend assigned.
Not all URLs must have the Isolation view icon.

When the Isolation View creates an icon without the backend assigned (Known issue) the map will be mounted with the whole Application filter instead the End to End transaction filter or If the application has more than 50k components, you will see the UI error as below:

 

 

Additional Information

There is a known error that AXA should not show the Isolation view icon to URLs that do not have a Backend call into it, as this leads the customer to misunderstand that it can mount the end-to-end transaction.
It is being discussed in a long-term resolution for future releases.