AWS probe generates duplicate alarms

book

Article ID: 196145

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

When the probe loses connection to an AWS account it alarms. It alarms one alarm with the hostname of the robot that houses the aws probe and one alarm with the hostname as the aws account name that can no longer connect.

Is that supposed to happen or is this something we have done to make it do that?

How can I make it so that ONLY the alarm with the Account name in it is the one that comes out so we don’t have duplicate alarms?

Cause

- UIM current probe framework

Environment

Release : 20.1

Component : UIM - AWS 5.41

Resolution

Yes, this is expected behavior that it generates two alarms, one alarm with the hostname of the robot/probe and one alarm with the hostname as the aws account name that can no longer connect.

As this alarm generation is not probe-specific this is from the UIM Framework. We saw the same behavior with all remote monitoring probes using the latest framework, please find below list of probes(which we tested) having the same behavior.

1. redis
2. hyperv
3. websphere
4. sap_basis
5. office365

and many more...

This would be major change to the UIM remote probe framework and needs to be tested with all the remote monitoring probes. That said, we may take up this in future releases of the framework.

Also, currently, there is no option to suppress one alarm in order to eliminate the duplicate alarms other than using the nas to manipulate the alarm, e.g., exclude it/close it.