StackState curated integration

This page describes StackState version 4.3.

The StackState 4.3 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.3 version range to upgrade to a more recent release.

Go to the documentation for the latest StackState release.


The SCOM StackPack is used to create a near real time synchronisation with your SCOM instance. The SCOM integration can be configured to run as either an API integration or PowerShell integration, these are described in the tabs below the diagram.

API integration

The StackState SCOM API integration sends requests to the SCOM API to retrieve topology data and events.

  • Agent V2 connects to the configured SCOM API.

  • Topology data and events for the configured criteria are retrieved from SCOM.

  • Agent V2 pushes retrieved data to StackState.

  • StackState translates incoming SCOM topology data into components and relations. Incoming events are used to determine component health state and publish SCOM alerts in StackState.

When to choose API integration

The SCOM API integration produces a clean topology in StackState by allowing you to specify the topology to collect. You can run the SCOM check from any StackState Agent V2 as long as it can connect to both the SCOM API and StackState.

Retrieving a large topology can require a high number of API requests, this can take time and may place some stress on your SCOM system. The size of topology you can retrieve may also be limited by the number of requests possible. To avoid this, use the SCOM PowerShell integration.



To set up the StackState SCOM API integration, you need to have:

  • StackState Agent V2 must be installed on any machine that can connect to both SCOM and StackState.

  • A running SCOM instance (version 1806 or 2019).

  • A SCOM user with the role Operations Manager Read-Only Operators.


Install the SCOM StackPack from the StackState UI StackPacks > Integrations screen. You will need to provide the following parameters:

  • SCOM Instance URL: the SCOM instance URL from which topology need to be collected.


To enable the SCOM check and begin collecting data from SCOM, add the following configuration to StackState Agent V2:

  1. Edit the Agent integration configuration file /etc/stackstate-agent/conf.d/scom.d/conf.yaml to include details of your SCOM instance:

    • hostip - SCOM IP.

    • domain - active directory domain where the SCOM is located.

    • username

    • password - use secrets management to store passwords outside of the configuration file.

    • auth_mode - Network or Windows (Default is Network).

    • integration mode - to use the API integration, set to api.

    • max_number_of_requests - The maximum number of requests that should be sent to the SCOM API. See how to determine the required number of API requests, default 10000.

    • criteria - A query to specify the components to retrieve data for.

        # run every minute
        min_collection_interval: 60
      - hostip: localhost
        domain: stackstate
        username: <username>
        password: <password>
        auth_mode: Network
        integration_mode: api    # can be api or powershell, default api
        max_number_of_requests: 10000   # default 10000
        criteria : "(FullName LIKE 'Microsoft.Windows.Computer:%')" # an Operations Manager Data Query
  2. Restart the StackState Agent(s) to apply the configuration changes.

Specify the components to retrieve data for

The components to retrieve data for can be defined using an Operations Manager Data Query ( For example, to retrieve data for all Microsoft Windows computers:

criteria : β€œ(FullName LIKE β€˜Microsoft.Windows.Computer:%’)”

Errors in the configured criteria query will be reported in the StackState Agent log file.

2020-11-05 09:19:31 GMT | ERROR | ... | ( | Invalid criteria :The property FullNsame is not valid for the given criteria.

Determine the required number of API requests

Use the script below to determine the number of components that match a criteria query and the number of dependencies. Add these numbers together and multiply by 2 to find the required number of API requests to retrieve topology data from SCOM. Two API requests are required to retrieve data for each component and each dependency.

$components = (Get-SCOMManagementGroup).GetMonitoringObjects("FullName LIKE 'Microsoft.Windows.Computer:%'")
"total number of components that match criteria: "+$components.count 
$deps= ($components.GetRelatedMonitoringObjects('Recursive')).count
"Total number of dependencies: "+ $deps

As two API requests are required to retrieve data for each component and each dependency, the configured max_number_of_requests must be higher than the returned total number of components that match criteria AND total number of dependencies multiplied by 2.


Integration status

To check the status of the SCOM integration, run the status subcommand and look for SCOM under Running Checks:

sudo stackstate-agent status

API connectivity (API integration only)

To check connectivity between StackState Agent V2 and the SCOM API, open the StackState Agent log file and search for the SCOM Connection Status Code. Connection status is reported as an HTTP status code - 200 is a good connection, other codes show a problem with connectivity.

( | Connection Status Code 200

Integration details

REST API endpoints

Retrieving topology data from SCOM requires 2 API requests per component.

API endpointDescription


Get type of component.


Get component information and relations.


Get alerts.

Data retrieved


Alerts and Health state from SCOM are available in StackState as events.



The following alert fields are retrieved: id, name, monitoringobjectdisplayname, description, resolutionstate, timeadded, monitoringobjectpath.

Health state

The component health state retrieved from SCOM is used to determine component health in StackState: Healthy = green Warning = orange Critical = red Not monitored, Out of contact or Maintenance mode = gray


The SCOM check does not retrieve any metrics data.


Retrieved topology data is visible in the StackState UI SCOM view, named *SCOM.* .

  • Components

  • Relations


The SCOM check does not retrieve any traces data.

Open source

The code for the StackState SCOM check is open source and available on GitHub at:


Troubleshooting steps for any known issues can be found in the StackState support Knowledge base.


To uninstall the SCOM StackPack and disable the SCOM check:

  1. Go to the StackState UI StackPacks > Integrations > SCOM screen and click UNINSTALL.

    • All SCOM specific configuration will be removed from StackState.

  2. Remove or rename the Agent integration configuration file, for example:

     mv scom.d/conf.yaml scom.d/conf.yaml.bak
  3. Restart the StackState Agent(s) to apply the configuration changes.

Release notes

SCOM StackPack v2.1.1 (2021-04-02)

  • Improvement: Enable auto grouping on generated views.

  • Improvement: Update documentation.

  • Improvement: Common bumped from 2.2.3 to 2.5.1

  • Improvement: StackState min version bumped to 4.3.0

SCOM StackPack v2.0.0 (2021-01-29)

  • Bugfix: Major bump the version for installation fix

SCOM StackPack v1.2.2 (2020-09-03)

  • Bugfix: Fix the problem of upgradation and installation.

SCOM StackPack v1.2.1 (2020-08-18)

  • Feature: Introduced the Release notes pop up for customer

SCOM StackPack v1.2.0 (2020-08-10)

  • Improvement: Deprecated stackpack specific layers and introduced a new common layer structure.

SCOM StackPack v1.1.0 (2020-04-10)

  • Improvement: Updated StackPacks integration page, categories, and icons for the SaaS trial

SCOM StackPack v1.0.1 (27-03-2020)

  • Bugfix: Fix the requirement of SCOM to run AgentV2 always.

SCOM StackPack v1.0.0 (15-01-2020)

This is the first public release of the SCOM StackPack that provides support to monitor your System Center Operations Manager instance. NOTE:- We support SCOM version 1806 and 2019.

  • Feature: Gathers Topology from your SCOM instance and allows visualization of your SCOM components and the relations between them.

  • Feature: Monitoring of your SCOM components, including health statuses of all your components.

See also

Last updated