System Center Operations Manager (SCOM) Poller
Description
The SCOM Poller polls for alerts from SCOM and sends them to 1Gateway.
Prerequisites
Installation
Make sure you have the 1gateway zip file that includes the plugin files and valid licences information ready. This file has been provided to you with the installation files.
1 - Login
Login to 1gateway, and make sure you are in "Advanced mode". If this is the first time you log in, the default user and password are both 'admin' (without the quotes).
2 - System Maintenance
Click on the menu icon and choose the option "System maintenance"
3 - Upload file
In the System maintenance view you can either drag and drop the downloaded zip file or select it by clicking the "choose file" button.
4 - Restart
After the upload installation will be confirmed. Restart 1Gateway to ensure any locked files are updated.
Configuration
Open the main menu and click on "New plugin"
Select the plugin you want to configure. Use the Filter field if needed.
Field name | Supported values | Description |
---|---|---|
SCOM server | Valid IP address or hostname | SCOM server. |
Windows username | Any string | Windows username (used for NTLM authentication) |
Windows password | Any string | Windows password (used for NTLM authentication) |
Windows domain | Any string | Windows domain (used for NTLM authentication) |
Filename | Path to JSON file | Path to a JSON file that defines the body of the POST request to get the alerts from SCOM |
Polling interval | Any integer | Polling interval in seconds (default is 300) |
The SCOM listener plugin requires the Windows credentials on the SCOM server for NTLM authentication.
The file content of the Filename defined in the configuration includes a filter used to decide which alerts to get from SCOM and the fields included in the response.
In this example there is a LastModified field included in the criteria. The value of this field will be overwritten with the LastModified field of the newest message that came in the last poll cycle.
A default LastModified value can be configured by a super user.
alerts_body.json
{
"classId": null,
"objectIds": {},
"criteria": "((Severity = '0') OR (Severity = '1') OR (Severity = '2')) AND ((Priority = '0') OR (Priority = '2') OR (Priority = '1')) AND ((ResolutionState = '0') OR (ResolutionState = '247') OR (ResolutionState = '248') OR (ResolutionState = '249') OR (ResolutionState = '250') OR (ResolutionState = '254') OR (ResolutionState = '255')) AND (LastModified >= 'LAST_TIMESTAMP')",
"displayColumns": [
"age",
"category",
"connectorstatus",
"timeadded",
"timeaddedutc",
"customfield1",
"customfield10",
"customfield2",
"customfield3",
"customfield4",
"customfield5",
"customfield6",
"customfield7",
"customfield8",
"customfield9",
"description",
"ismonitoralert",
"lastmodified",
"lastmodifiedby",
"lastmodifiedutc",
"latency",
"monitoringobjectinmaintenancemode",
"monitorname",
"name",
"netbioscomputername",
"netbiosdomainname",
"owner",
"monitoringobjectpath",
"principalname",
"priority",
"repeatcount",
"resolutionstate",
"resolvedby",
"severity",
"sitename",
"monitoringobjectdisplayname",
"statelastmodified",
"statelastmodifiedutc",
"tfsworkitemid",
"tfsworkitemowner",
"ticketid",
"timeresolutionstatelastmodified",
"timeresolved",
"timeresolvedutc",
"classid"
]
}