Ping Availability ETI in node down events

Hi All,

We have integrated OMW to OMi. A node down message coming from OMW has ETI "Ping Availability: Unavailable" automatically, which sets the status of "System Availability" KPI to critical. This is ok.

But when node up message comes (normal), it acknowledges the node down message, but it does not have any ETI. Thus the CI status (its KPI) remain to be critical even if the node has come up.

The question is how I can put ETI "Ping Availability: Available" in the normal message so the it sets the KPI as normal/green in OMi dahsboards.

 

Parents
  • Verified Answer

    Hello,

    This issue can be resolved by creating a new filter called "PingAvailabilityFilter" which is a copy of the "PingUnAvailabilityFilter". The new "PingAvailabilityFilter" should be configured for messages of severity "Normal" where the title contains the words "is now running” and then the "Ping Availability" indicator can be modifed to use the "PingUnAvailabilityFilter" and new "PingAvailabilityFilter".

    This should resolve the problem you see.

    Regards,

    Colin

Reply
  • Verified Answer

    Hello,

    This issue can be resolved by creating a new filter called "PingAvailabilityFilter" which is a copy of the "PingUnAvailabilityFilter". The new "PingAvailabilityFilter" should be configured for messages of severity "Normal" where the title contains the words "is now running” and then the "Ping Availability" indicator can be modifed to use the "PingUnAvailabilityFilter" and new "PingAvailabilityFilter".

    This should resolve the problem you see.

    Regards,

    Colin

Children