Consecutive errors values reported with ASM agent does not match with ASM alert setup
search cancel

Consecutive errors values reported with ASM agent does not match with ASM alert setup

book

Article ID: 387464

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We are observing an issue where the value of Consecutive errors metric that is reported with ASM agent and the value of Consecutive errors that is reported within ASM alert setup does not match.

The ASM agent is quite latest and using the ASM Streaming API to get the data from ASM.

The ASM agent reports Consecutive errors value for a monitor. The observation is that this value is not being reported correctly. This value has been working good for past many years, but it seems to change recently (the logic of this value is changed from earlier logic). Where as the Consecutive errors that is reported within ASM alert setup continue to function as before but value reported by ASM agent changed as the agent reported before recent changes.

This is being observed when an APM alert is being setup on monitor with 5 minutes check.

If we set the alert for Consecutive errors with value of 2, it should alert after 10 minutes.  First error at 5 minutes interval and second error at 10 minutes interval. But the observation is that the alert is being triggered after 5 minute. Also, at 5 minutes interval we find that the Consecutive errors metric reporting value of 2.

Where if we setup an alert on ASM side with alert after 2 Consecutive errors, it continue to function properly and sending ASM alert after 10 minutes. 

Resolution

Provided new ASM agent which seems like working as expected. This fix will be included in release 25.3.2 (which will be in March).