Experience card stats for APIs double

book

Article ID: 194396

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

 
Using Precision API Monitoring 3.4, the stats in APM are inflated for calls to API Gateway.
 
For example, calling an API 10 times, this reflects in the APM Team Center experience card as 20 calls.


Initially the experience card was showing multiple experiences but even filtering to one experience, the transaction count was still double

The Services metrics total requests counts are accurate in the Introscope Metric Browser.

Cause

 

The transaction counting in experience cards relies on counting Frontend transactions. This can also be Business Transactions and indeed in this integration, the left-most component seen to start the transaction was a Business Transaction component.

In Precision API monitoring, Frontend metrics (and Business Transaction metrics) are created by copying the relevant values received for Services metrics. This is done using a Javascript, apim.js, deployed to the Enterprise Manager.

On further inspection, the Frontend metrics did show double counting of transactions. In particular, for one API call, there would be two consecutive responses logged in two separate 15-second intervals. 

 

In this particular scenario, there were actually two copies of the script in the Enterprise Manager's scripts folder. As well as apim.js, there was a renamed script suggesting it was part of Precision API monitoring 3.2

Environment

 

Release : 10.7.0

Component : APM TEAM CENTER/ACC

Using Precision API Monitoring 3.4

Resolution

 

The solution was to remove the duplicate apim.js file