Page tree
Skip to end of metadata
Go to start of metadata

Overview

System Center Operations Manager (SCOM) is a data center monitoring system for operating systems and hypervisors. It provides alerts and alarms generated according to availability, performance, configuration or security situations. This document describes the configuration required to establish a connection between the SCOM Server and the SCOM LAM in Moogsoft AIOps using an SCOM Connector.

The SCOM Server and the SCOM LAM communicate with each other using the SCOM Connector. The SCOM Connector performs following actions:

  • Data collection: Retrieve events/alerts from an entity. This collection happens on a defined time schedule, for example, every 60 seconds
  • Data normalization: Format, cleanse, filter and normalize the retrieved data into an event that can be sent to SCOM LAM
  • Emit the events: Send the normalized event to SCOM LAM
  • Update the source: Moogsoft AIOps also has the ability to update an entity with information collected from SCOM. When a Moogsoft AIOps user wants to update the entity in any way, they can use a number of predefined user actions to send the Microsoft SolutionPak with Moogsoft AIOps messages indicating that an attribute within a given entity is to be updated, e.g. an alert within SCOM (Systems Center Operation Manager) being changed from resolved to closed

Process Workflow

The workflow of gathering alarms from an SCOM Server and publishing it to Moogsoft AIOps is as follows:

  1. SCOM Connector reads the SCOMConnectorConfig.json file.
  2. SCOM Connector uses the input from SCOMAddressHost, userDomain, userID and UserPassword fields in the SCOMConnectorConfig.json to connect with the SCOM Server.
  3. SCOM Connector retrieves new or updated events/alerts from the SCOM Server.
  4. SCOM Connector parses the event/alert data and creates a JSON data containing the parsed event/alert.
  5. SCOM Connector sends the JSON data to the SCOM LAM which publishes the alerts/events on the Moogsoft AIOps GUI.
  6. SCOM Connector accepts an HTTP POST request from MOOBOT about the status change in alerts/events.
  7. SCOM Connector updates the event/alert status on the SCOM Server.

SCOM Connector (Basic) vs SCOM Connector (Advanced)

There are two variants of SCOM Connector that can be be used to fetch alerts from SCOM. The basic version of SCOM Connector does not support HA functionality and also does not allow installation of multiple instances of SCOM Connectors on the same machine. If HA functionality or multiple instances of SCOM Connector are required, then the SCOM Connector (Advanced) should be installed. The list of features of SCOM Connector (Basic) and SCOM Connector (Advanced) are as follows:

SCOM (Basic)

  • Automatic Service Restart of the SCOM Connector service
  • Separate config file to save the last poll time stamp. The name of this config file is SCOMLastPollTime.json
  • Supports communication through proxy
  • Windows Event Logging
  • Option to stop SCOM Connector starting automatically after installation. If this option is chosen, the connector has to be started manually after installation
  • Alert Storm Threshold can be entered in the Installer GUI
  • Some important configurations can be edited from the GUI
  • Support for Multiple Moog
  • Alert is sent to Moog if any of the added SCOM Server goes down
  • Alert is sent to other Moogs if one of the Moogs, in a Multi Moog setup, goes down

SCOM (Advanced)

  • Multiple SCOM Connector instances can be installed on the same machine
  • The service names of the SCOM Connectors can be configured through the Installer GUI. Once configured, the service name cannot be changed
  • Management Group support for SCOM Connectors. One Connector supports only one Management Group. To fetch events from multiple Management Groups, multiple SCOM Connectors are to be installed
  • The SCOM servers added to an SCOM Connector are assigned a priority. The SCOM Connector fetches the alerts from the server having the highest priority. If the server assigned the highest priority fails, then the SCOM Connector connects with the next available server and so on
  • Infinite retry attempts is supported. Enter "-1" in the "AmountOfTimeouts" field of SCOMConnectorConfig.json file. By default, it is set to "-1"
  • The SCOM Connector can fetch alerts only up to 10 times the "AlertPollCycleTime". This is the case if the duration from the last poll time is greater than 10 times of "AlertPollCycleTime" . If the duration is less than 10 times the "AlertPollCycleTime", then the alerts are fetched from the last poll time
  • The SCOM Connector has separate folders for logs and config files. The Config file is saved in the Configs directory of the Installer folder, while the logs are saved in the Logs directory of the Installer folder
  • The configurations are saved even after uninstallation. If you uninstall the SCOM Connector and then reinstall it from the same folder, then the previous configurations are automatically filled in the installer GUI
  • The status page will show either the SCOM Server with the highest priority or the server from which the SCOM Connector is fetching events
  • Automatic Service Restart of the SCOM Connector service and the MCM Service
  • Separate config file to save the last poll time stamp. The name of this config file is SCOMLastPollTime.json
  • Different SCOM Servers can be added to Primary and Secondary SCOM Connectors
  • Supports communication through proxy
  • Windows Event Logging
  • Option to stop SCOM Connector starting automatically after installation. If this option is chosen, the connector has to be started manually after installation
  • Alert Storm Threshold can be entered in the Installer GUI
  • Some important configurations can be edited from the GUI
  • Support for Multiple Moog
  • Alert is sent to Moog if any of the added SCOM Server goes down
  • Alert is sent to other Moogs if one of the Moogs, in a Multi Moog setup, goes down
  • No labels