Application is impacted due to browser agent as DXC was down

book

Article ID: 213136

calendar_today

Updated On:

Products

CA Application Performance Management SaaS

Issue/Introduction

This happened before.

If the DXC services are not running, then the application is impacted, as page tries to contact the DXC with the injected scripts in the code.

Then, it is unable to find it and tries to load that script continuously that causes the slowness.

 

Need to know a method on how this can be avoided if DXC is down. And as a result, the application should not be impacted.

Java agent -- 10.7 and on-premise APM

Browser agent -- 10.7

 

Environment

Release : SAAS

Component : APM SAAS ENTERPRISE

Resolution

Please enable ASYNC in  ../config/default.basnippet.

 

As you know, the Browser Agent is tightly coupled with DXC for all communications with APM/AXA. As such, all of these calls are asynchronous and do not wait for responses. 

In the script provided, there is no Async property. 

 

Please ask the customer to try the below and add the async parameter added to below in the end:

 

<script type="text/javascript" id="ca_eum_ba" src="{protocol}://{host}:{port}/api/1/urn:ca:tenantId:default-tenant/urn:ca:appId:default-app/bajs?agent=browser" data-profileUrl="{protocol}://{host}:{port}/api/1/urn:ca:tenantId:default-tenant/urn:ca:appId:default-app/profile?agent=browser" data-tenantID="default-tenant" data-appID="default-app" data-appKey="b0361800-4736-11e6-b8e5-bddc75280658" async></script>

 

OR dxc may also support the below too: 

 

<script type="text/javascript" id="ca_eum_ba" src="{protocol}://{host}:{port}/api/1/urn:ca:tenantId:default-tenant/urn:ca:appId:default-app/bajs?agent=browser" data-profileUrl="{protocol}://{host}:{port}/api/1/urn:ca:tenantId:default-tenant/urn:ca:appId:default-app/profile?agent=browser" data-tenantID="default-tenant" data-appID="default-app" data-appKey="b0361800-4736-11e6-b8e5-bddc75280658" async=true></script>