Important: You do not need to install the S.o.S add-on on a Splunk instance where the S.o.S app is already installed. The S.o.S app ships with the same data inputs.
This S.o.S add-on allows you to pull in resource usage data from remote Splunk instances running on Windows for display in your existing instance of the Splunk on Splunk app. To enable this, install and configure this S.o.S add-on on Windows search-peers or forwarders to track the resource usage of Splunk.
NOTE: You must enable the data inputs included in this add-on before they can report resource usage information. By default, these inputs are disabled. Refer to the README file for more information.
For more details on how to set up S.o.S and its add-on to monitor Splunk's system resource usage, please refer to the following Splunk Answers:
[SUP-812] Fixed an issue where ps_sos.ps1 would often produce errors referencing calls to a method with a null-valued expression.
[SUP-845] Replaced all mentions of the S.o.S "technology add-on" with "add-on".
[SUP-691] Fixed an issue where the ps_sos.ps1 scripted input produced format errors when trying to set $CMDLINE.
[SUP-718] Made the ps_sos.ps1 scripted input more resilient to errors.
[SUP-672] Added an index definition for 'sos_summary_daily index' to indexes.conf.
[SUP-616] Fixed an issue with the ps_sos.ps1 scripted input where memory usage would sometimes be recorded as a negative value.
[SUP-565] Fixed an issue where the ps_sos.ps1 scripted input would not run on an instance part of a search-head pool.
[SUP-541] Updated the app icon.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.