2621 views

Description

The SCOM connector groovy script contains regressions:
- Alerts from SCOM do not close in ServiceNow despite receiving value 255 (=closing)
- SCOM groovy script does not collect SCOM alerts with empty Node field
- Time of SCOM event is set to the time of the SN instance, not original time when the Alert was created in SCOM server

Steps to Reproduce

 

  1. Activate Event Management plugin.
  2. Define SCOM connector.
  3. Activate SCOM connector.
  4. Notice the following:
    • There are no incoming events with resolution state Closing - no alert will be closed
    • There are no incoming events with empty Node field
    • The Time of event is the time of the event created in the SN instance and not when it was created in the SCOM server

Workaround

To resolve the resolution state issue, create an Event Mapping Rule that maps the value 255 in the field ResolutionState to the value Closing.

To resolve all of the issues, replace the SCOM script with the attached SCOM script.


Related Problem: PRB651320

Seen In

Fuji Patch 9 Hot Fix 1

Fixed In

Fuji Patch 11
Helsinki

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-07-25 12:30:27
Published:2016-02-09