Consider the following use case: OBM receives and event which resolves to a CI and Health Indicator (HI). That event sets the HI to a “non-normal” status. In addition, you don’t have a “back-to-normal” event to reset the HI status whenever the issue is resolved. Instead of that either you close the event from the Events Browser, or by script whenever a Ticket (which was created from the event) is resolved or by Time-Based Event Automation (TBEA). In OBM the HI’s lifecycle is independent of the event’s lifecycle, which means if you don’t have “back-to-normal” events then you need to reset the HI in addition to closing the event. Otherwise, you can have a Service Health view which shows “non-normal” statuses, but the CIs don’t have any unresolved (i.e. active, open) events. This document provides a Groovy script which you can use in TBEA in order to reset the HI, in addition to modifying the event’s lifecycle (i.e., – closing the event).
Suggested for you are based on app category, product compatibility, popularity, rating and newness. Some apps may not show based on entitlements. Learn more about entitlements.
Added capability to run Reset HI via curl and not by opening HTTP connection.
The OBM Content Pack contains groovy script for Automation.
Refer to the ReadMe pdf document for further details.
Please upgrade to one of the following broswers: Internet Explorer 11 (or greater) or the latest version of Chrome or Firefox
