Integrate with Microsoft SCOM

What does the integration offer?

Integrate SCOM with Compass to forward both Operations Manager alerts and updates to Compass and benefit from Compass’s actionable alerts, powerful on-call schedules, escalations and reporting services. Microsoft System Center Operations Manager forwards alert events to Compass to create alerts and acknowledge, close, and add notes to them using PowerShell. Read more about PowerShell. Benefit from Compass’s alert deduplication by using SCOM integration. Read more about alert deduplication.

How does the integration work?

When an alert is created on SCOM, an alert is created in Compass automatically through the integration.
When an alert is resolved or closed on SCOM, the related alert is closed in Compass.
When an alert is acknowledged on SCOM, the related alert is acknowledged in Compass.

Supported versions

Following are the versions of Windows the integration supports:

Windows Server 2012 R2 (Windows Server 2012 works too)
Windows Server 2016
Windows Server 2019
Windows Server 2022

Following are the versions of SCOM the integration supports:

System Center Operations Manager 2012 R2 (SCOM 2012 works too)
System Center Operations Manager 2016
System Center Operations Manager 2019
System Center Operations Manager 2022

The integration is not tested on the 2018 releases of SCOM, but it can also work on:

System Center Operations Manager 1801
System Center Operations Manager 1807

Set up the integration

SCOM is an API-based integration. Setting it up involves the following steps:

Add a SCOM integration in Compass
Configure the integration in SCOM

Add a SCOM integration

In this release, only incoming integrations are fully supported in the Standard plan, at a team level. To use outgoing integrations or the outgoing part of bidirectional integrations, upgrade to a higher subscription plan. There may be restrictions on how you can create and apply integration rules as well.

You can add this integration only from your team’s operations page. Adding an integration from your team’s operations page makes your team the owner of the integration. This means Compass only assigns the alerts received through this integration to your team.

To add a SCOM integration in Compass, complete the following steps:

Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “SCOM”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the integration URL.
You will use this URL while configuring the integration in SCOM later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Microsoft SCOM

To configure the integration in SCOM, complete the following steps:

On each SCOM application host in your cluster, create a new folder by name ”jsm” under your root scripts directory. The path should be C:\scripts\jsm.

Download the Compass's SCOM PowerShell Script. Copy it into the directory created in Step 1. Make sure that the name of the script file is “jsm.ps1” and its path is C:\scripts\jsm\jsm.ps1.

Minimum requirement for Powershell

The minimum version of Powershell required for the script to work is 3.0. If you’re using a version older than 3.0, you’ll need to develop the Powershell Script code for converting the values into JSON and posting the HTTP request to Compass yourself.

Install the PowerShell script:

3.a.) Open an elevated command prompt.

3.b.) Unblock the script file if you haven’t done so already.

Powershell -command "Unblock-File C:\scripts\jsm\jsm.ps1"

Repeat this step on all the SCOM application hosts in your cluster.

3.c.) Run the following command:

Powershell -ExecutionPolicy bypass -file C:\scripts\jsm\jsm.ps1 -Url [integration url] -install

Repeat this step on all the SCOM application hosts in your cluster.

Sample payload sent from SCOM

(in JSON format)

{
  "owner": "np",
  "lastModified": "12/24/2015 11:47:16 AM",
  "resolutionState": "New",
  "timeRaised": "12/24/2015 11:47:16 AM",
  "resolutionStateLastModified": "np",
  "workflowId": "{7eba60fd-b179-69a7-3897-47b6753601f2}",
  "category": "Custom",
  "alertId": "{2ba87d56-a7af-4b42-bdcc-eb18486bd8cd}",
  "alertName": "Alert for event 999",
  "priority": "1",
  "severity": "2",
  "createdByMonitor": "false",
  "repeatCount": "0",
  "alertDescription": "np",
  "managedEntitySource": "WIN-RQTU8UB5TU5.jsmscom.com"
}