Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Get started with Operational Intelligence

Log in to subscribe to topics and get notified when content changes.

Get started with Operational Intelligence

Complete the following setup and initial configuration steps to start using Operational Intelligence.

About this task

Raw metric data, collected by data sources such as Microsoft System Center Operations Manager (SCOM), needs to reach the Operational Intelligence MID Server for processing and analysis. You can set up Operational Intelligence to receive raw metric data from external data sources using either pull or push mechanism.

Using either method (pulling or pushing) requires the configuration of the ITOA MetricExtension MID Server extension. The main roles of this extension are to normalize the raw data, and to detect any anomalies. The normalized data and anomalies (if above the specified threshold), are then transmitted to the instance.

Some of the steps below for setting up Operational Intelligence, must be completed regardless of the method used. Other steps depend on the method used for transmitting data between the data source and the MID Server:

Pulling

This method requires using a connector that is configured to pull data from the specific data source that is collecting the raw data. You can use a pre-defined connector such as SCOM (which was previously defined for pulling events from SCOM), Azure, or AWS, or configure a new custom connector specifically for the external source that is used in your environment.

Pushing

This method uses web service APIs and is based on client-side tools that push the raw data from the external source to the MID Server. This method requires that the ITOA MetricExtension extension is configured with the Enable REST Listener option enabled.

You also need to configure the Web Server extension, which starts a Web Server on the MID Server. Request handlers are added on the Web Server that listen to any incoming metric data that was pushed from the external source.

Watch the Event Management | Collecting Events and Metrics short video about using MID Servers for pulling and pushing metric data.

To set up Operational Intelligence you can complete the following procedure. Alternatively, you can follow a prescribed step-by-step guidance. Navigate to Guided Setup > ITOM Guided Setup, and click Continue. Then scroll to Operational Intelligence, and click Continue. For more information, watch the Operational Intelligence | Setup short video.

Procedure

  1. Activate the Operational Intelligence plugin.
  2. Configure a MID Server and a MID Server distributed cluster for Operational intelligence: Create a MID Server cluster with the Distributed type. Then add to that cluster at least one MID Server with the required hardware, software, and other configurations, and with the ITOA Metric capability from the Operational Intelligence plugin. If the default SCOM connector is used, then the same MID Server that is used to collect events, should be used for Operational Intelligence.
  3. Configure the Operational Intelligence extension.
  4. To configure for pulling:
    1. Create a connector definition (For a SCOM connector - this is already defined for pulling events from SCOM).
    2. Configure metric connector instances to pull metric data from SCOM, Microsoft Azure, or Amazon Web Services (AWS). For other data sources, see Configure a connector instance.
  5. To configure for pushing:
    1. Configure the MID Web Server extension.
    2. In the ITOA MetricExtension extension, ensure that the Enable REST Listener option is enabled, and that the MID Web Server Extension is set.
    3. Create the client scripts that push the raw data from the external source to the MID Server.
  6. Create or configure metric type registration.
  7. Choose and configure metrics to monitor.
  8. Create event rules to map raw metric data to specific CI types.
Feedback