Spectrum is integrated with SCOM.
When the SCOM connector is restarted or there is a failover from the Primary SpectroSERVER to the Secondary SpectroSERVER, SCOM is sending a new "empty" alarm to Spectrum for all existing alarms.
If an Event Rule or Procedure is attached to the out of the box SCOM event, this also produces an "empty" custom event generated from the rule or procedure.
The following is an example:
Device scomserver of type Host_Device - System Center Operations Manager has reported a warning. -
Description: This event re-asserts the alarm.
Created:
Owner:
Severity:
Priority:
Repeat Count:
Resolution State:
Alert URL - http://scomserver:80/OperationsManager/default.aspx?DisplayMode=Pivot&AlertID=60787bcc-04d8-4287-8663-742849c660cf
Category
ConnectorID
Context
Desctription This event re-asserts the alarm.
Alert Id
IsMonitorAlert
LastModifiedByNonConnector
LastModifiedBy
LastModified
MaintenanceModeLastModified
ManagementGroup
ManagementGroupId
MonitoringClassId
Source
MonitoringObjectFullName
Severity
MonitoringObjectID
MonitoringObjectIDInMaintenanceMode
MonitoringObjectDisplayName
RuleId
Name
NetbiosComputerName
NetbiosDomainName
Path
Priority
RuleId
ResolutionStateDigit
ResolutionStateName
Severity
TimeRaised
TimeAdded
TimeResolutionStateLastModified
StateLastModified
Path
Out of the box, during a SCOM restart or an SS failover occurrence, SCOM sends an "empty" out of the box event to Spectrum. This is associated with the current SCOM alarm/event so the alarm does not go stale.
Release : Any
Component : Spectrum Integration/SCOM
This is functioning as designed.