Distinguishing what is actively monitored from what is not.

[FrankyVally]

Hello,

We have integrated a couple of HP monitoring software together:

BSM

UCMDB

UD

OMW

NNMi

SiteScope

BPM

SIM

The automatic discovery of NNMi and UD is turned on.  So soon after a new server for a project that is not yet in production is turned on, it is discovered and starts sending alarms (reboot for example).  In NNMi, we were using a custom attribute to decide if the alarm/incident was to be displayed/emailed/paged.  This work well for us.  Now that all the monitoring products send their alarms to OMi, we are looking for the best way to reproduce this in OMi.

We thought about maybe creating a field in the CI to specify the status.

How does the other users does this?

Thanks and regards,

[Asaf Shechter]

as you mentioned, you can use CI attribute to distinguish the CI state. you can leverage OOTB field such as Environment or create your own. anyway, you will also need to enhance your Events after the resolved to the CI in order to decide what to do with them.