ServiceNow Operational Intelligence Complete Setup and Step-by-Step configuration

[Sayali_Suryawan]

Hello Experts,

I am sharing the setup and step-by-step configuration for Metric Intelligence, previously known as Operational Intelligence. Metric Intelligence is an add-on application to Event Management that enables IT teams to analyze performance issues within IT infrastructure and applications.

Requirements 

Properties : 

• The property sa.metric.display.mid.setup.action set to true. 
• Default Value - True

Plugins : 

• Plugin - Metric Intelligence(sn_metrics_ng)
• Performance Analytics - Content Pack - Operational Intelligence(com.snc.sa.metric.pa.content)

Operational Intelligence Setup and step-by-step configuration.

• Operational Intelligence MID server
• Metric Type
• Operational Intelligence Connectors
• Event Rule
  
  

Step A: Operational Intelligence MID server
The MID server setup is divided into two parts: Automated Configuration and Manual Configuration. Both steps need to be completed.

For example, we demonstrated the SolarWinds source and connector for Operational Intelligence (OI).

Automated Configuration: 

• Your Instance - Select MID server - Open MID Server record - Click on “Setup Metric Intelligence” on related links
• It will create the below things for Operational Intelligence

1 - Extension Contexts (ecc_agent_ext_context) : Operational Intelligence Metrics

To check go to - Navigation - MID server - Open record - Extensions - Profile and deployments - Metric Intelligence

2 - MID Server Cluster (ecc_agent_cluster)

Navigation - MID server - Clusters

3 - Added Supported applications (ecc_agent_application): Operational Intelligence

Navigation - MID server - Clusters - Applications

4 - Added Metrics to Capabilities (ecc_agent_capability_m2m): Metrics

Open the MID server - related list - Capabilities - Metrics

Manual configuration:

1 - Add Capabilities

MID Server - Server - Open record - Related list - Capabilities - Edit - Add REST, AgentClientCollector, and Monitoring

2 - Check whether Event Management is added to the supported application; if not, add it.

3 - Add MID Web Server (ecc_agent_ext_context_webserver)

Navigation - MID Server - Server - Open record - Related list - MID Server Extension Contexts - New - Mid Web Server Context

Fill the mandatory fields Name

HTTP/HTTPS Port - 443 or 80 are default port number, you can use any of this - Save

Start the Mid web Server Context

4 - Add ACC Websocket Endpoint (sn_agent_ext_context)

Navigation - MID Server - Server - Open record - Related list - MID Server Extension Contexts - New - ACC Websocket Endpoint

Fill the mandatory fields Name

Save and Start

5- Enable REST Listener for OI

Navigation - MID Server - Server - Open record - Related list - MID Web Server Extension - Open OI extension record and click on “Setup REST Listener” . It will add MID web server extension to OI extension.

And check status is started if not, then click on restart

Step B: Metric Type

1 - Register Metric
Navigation - sa_metric_registration.LIST 
Open the Solarwind records - Active the "Registration mode" and "Type default mode"

It will register the solarwinds and initiate the collection metric type automatically.

2 - Metric to monitor
Navigation - Event management - Metric Type - Check whether the SolarWinds metric types are being received. In some cases, they may be generated immediately, while in others, it could take several days.

Now change the state of all solarwinds meric type "Anomaly detection action level” to “Anomaly alerts”. It will further create anomaly alerts for the events. And monitor CIs bounds. Also give you analytical views. You can change the state of all metric types through a fix script.

Step C: Operational Intelligence Connectors

1 - Connector Definition 

Navigation - Event Management - Integrations - Connector Definitions

Select the source record “SolarWinds” - “Collect metrics” - True - Save. 

2- Connector Instance

Navigation - Event Management - Integrations - Connector Instance

• Open - SolarWinds connector  -  “Enable Metric Collection” - and  add “MID server” to the related list MID Servers for Connectors 

And click on “Test Connector” 

Note: If you have two connectors, you can enable metric collection for both instances. Make sure the MID server is added to the related list “MID Servers for Connectors” before running the test.

Step D- Event Rule

Navigation - Event management - Event rule - New - Click on the“Event Rule Info” tab Source - “SolarWinds” and “Event Filter” tab - Classification - is - metric” - Save

There are some OI scheduled jobs running on the backend. These are OOB jobs.

Now your setup is completed!!!

You can check the output through various methods, including the event rule, anomaly alerts, Metric Intelligence dashboard, Metric to CI table, anomaly maps, and Insight Explorer.

Kindly mark my post as helpful, and feel free to ask me any questions if you have them.