Hardware and software requirements for the Splunk Add-on for Microsoft SCOM

Splunk admin requirements

You must be member of the admin or sc_admin role.

Microsoft SCOM requirements

To collect data, the Splunk Add-on for Microsoft SCOM must be installed on a Splunk Enterprise forwarder or single instance Splunk Enterprise that is installed on the same machine as your Microsoft System Center Operations Manager 2019 Operations console. All of the hardware and software requirements for your Microsoft SCOM instance apply to this add-on when it is installed on the data collection node. Configuration tasks that depend on Microsoft Windows and SCOM components may not work when the add-on is not installed on Windows.

The Splunk Add-on for Microsoft SCOM supports distributed deployments of SCOM in which management servers are installed separately from the operations console. If you have management servers for which you want to collect SCOM data installed on separate machines from your operations console, you must have an administrator account, or another account that has read permissions for the commands you use to collect SCOM data, on your management server in order for the Splunk Add-on for Microsoft SCOM to collect the metrics from the remote server.

The Splunk Add-on for Microsoft SCOM version supports Microsoft SCOM clustered environments. You can collect metrics from more than one node in a SCOM cluster.

PowerShell and .NET framework requirements

The following software must be installed on the same machine as your Microsoft System Center Operations Manager 2019:

• PowerShell v3 or later
• Microsoft .NET framework v4.0 or later

You do not need to install the Splunk Add-on for Microsoft PowerShell with this version of the Splunk Add-on for Microsoft SCOM, because Splunk platform versions 6.3 and later contain a native PowerShell modular input.

Splunk platform requirements

Because this add-on runs on the Splunk platform, all of the system requirements apply for the Splunk software that you use to run this add-on.

• For Splunk Enterprise system requirements, see System Requirements in the Splunk Enterprise Installation Manual.
• If you plan to run this add-on entirely in Splunk Cloud, there are no additional Splunk platform requirements.
• If you are managing on-premises forwarders to get data into Splunk Cloud, see System Requirements in the Splunk Enterprise Installation Manual, which includes information about forwarders.

For information about installation locations and environments, see Install the Splunk Add-on for Microsoft SCOM.

Sizing guidelines and performance data

A single-instance deployment of Splunk Enterprise performed data collection at the rates and volumes listed below.

Events per second	Average CPU usage	Max memory usage	Average event size
66.8	8.23	3.1 GB	1.25 KB

Performance impact with the Splunk Add-on for Microsoft SCOM 2.3.0 on Splunk 7.3.x

The Splunk Add-on for Microsoft SCOM 2.3.0 on Splunk 7.3.x has the following performance impact:

• Events are ingested immediately after the Add-on script is executed
• Events per second is lower because serialization happens immediately after the Add-on script is executed instead of after all objects are collected
• Memory consumption is improved

Trial 1

No. of events	Add-on version	Splunk version	Script execution time	Execution vs ingest time 1	Average CPU usage	Max memory usage	Events per second
50000	2.3.0	7.2.x	61 min	61 min	25.925	991.91 MB	35.88
50000	2.2.0	7.2.x	61 min	61 min	27.9	1.49 GB	30.49
50000	2.3.0	7.3.x	91 min	1 sec	25.7	117.48 MB	12.06
50000	2.2.0	7.3.x	94 min	60 min	30.4	740 MB	30.83

1. The approximate time between the execution of the Add-on command and ingesting the first event index into Splunk.

Trial 2:

No. of events	Add-on version	Splunk version	Script execution time	Execution vs ingest time 1	Average CPU usage	Max memory usage	Events per second
50000	2.3.0	7.2.x	65 min	65 min	27	1 GB	33.67
50000	2.2.0	7.2.x	65 min	65 min	26.5	1.45 GB	32
50000	2.3.0	7.3.x	82 min	5 sec	28	230 MB	11.2
50000	2.2.0	7.3.x	95 min	61 min	32	750 MB	33

1. The approximate time between the execution of the Add-on script and ingesting the first event index into Splunk.