search cancel

How Does AXA Determines which Transactions are Flagged as Slow?

book

Article ID: 15078

calendar_today

Updated On:

Products

DX Application Performance Management

Issue/Introduction

    In AXA, Slow Transaction are defined as...

Slow Transactions: Dynamic computation of slow transaction marks a transaction as slow if the transaction takes at least 1000 milliseconds to complete or takes longer than the moving average of the completion time for the selected time period.

Source: https://docops.ca.com/ca-app-experience-analytics/16-4/en/using/axa/app-transactions



    What computations are performed to determine if a transactions is slow? Does AXA allow user configuration changes to define when transactions are flagged as slow?

Environment

AXA version 16.4.2

Resolution

    AXA, by default, defines a slow transaction as any transaction that exceeds 1000 ms. This process is used until 1000 transactions are recorded. After 1000 transactions have occurred, AXA switches to a moving average that considers the previous 1000 transactions and alerts if the transaction time was higher than the calculated average of the last 1000 transactions.

Users can change the slow transaction alerting threshold, on a per application basis, by manually defining an Alert. This is done under the "Alerts".

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKfIAAW" alt="Alerts.png" width="1345" height="393">

Click "Alerts" then "Set & Edit Alerts" (Note you need to have filtered on a specific application for the alert thresholds to display.)

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKfJAAW" alt="SetandEdit.png" width="1355" height="469">

Then under, "Transaction Duration", you can manually define an alert.

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKfKAAW" alt="TransactionDuration.png" width="1360" height="631">

Any manually defined alert will take precedence over AXA's default logic. For more information on defining alerts, see:
https://docops.ca.com/ca-app-experience-analytics/16-4/en/using/axa/manage-alerts

 

The default behavior alerting behaviors of AXA can also be modified:

1. To change the static 1000 ms alerting threshold used for all applications with less than 1000 reported transactions....

-Navigate to $AXA_HOME/conf/mdo-aggregator_instance.properties
-Edit the property "asat.slow.threshold = 1000" with the new desired threshold in ms.
-Restart the Aggregator Process by navigating to $AXA_HOME/bin and running the following commands:
./stopServices.sh -A
./startServices.sh -A

 

2. To update the number of transactions used for to calculate the moving average....

- In your AXA rdbms instance, run the following update statement:

Update ARCMNCONFIG set paramvalue='<number of transactions>' where paramname='MDO.SlowTxnAvgSampleMinCount';
Commit;

For example, the following would update AXA to use 500 transactions in moving average calculations:

Update ARCMNCONFIG set paramvalue='500' where paramname='MDO.SlowTxnAvgSampleMinCount';
Commit;

-Restart AXA by navigating to $AXA_HOME/bin and running the following commands:
./stopServices.sh -axa
./startServices.sh -axa

 

Additional Information

    As always,  contact CA Support if you have further questions.

Attachments

1558718219144000015078_sktwi1f5rjvs16uv4.png get_app
1558718216853000015078_sktwi1f5rjvs16uv3.png get_app
1558718214808000015078_sktwi1f5rjvs16uv2.png get_app