The NIPING utility can be used to track SAP system availability directly from your Splunk environment. Currently, this will only work if your Splunk environment is hosted on the same internal network as your SAP environment. If you Splunk deployment is hosted on the same internal network as your SAP environment, it may be easier to configure the PowerConnect Splunk app’s built-in NIPING utility. However, you may still use this option instead.
Please note the following requirements for running the standalone NIPING utility:
A separate host system running Windows or Linux outside of your SAP deployment running on the same internal network.
Python 3.6+ with the httplib2 library installed.
Please note that installation is written without regard to the operating system, so consult external resources for OS-specific issues.
Download the standalone NIPING utility
Extract the NIPING utility to the desired folder
Find the NIPING utility executable for your host’s operating system in an SAP install directory (..\usr\sap\<SID>\D<instance enumeration>\exe)
Copy the NIPING utility and associated library files to the utility’s /lib/niping directory
Configure the target_hosts.ini file using the instructions provided within the file
You will need the following for each target SAP host:
host IP address
port (use 3200 as the default unless directed to use a different port by your BASIS team)
Configure the target_endpoints.ini file using the instructions provided within the file
You will need the following for each target Splunk deployment:
URI (host address)
For Splunk Cloud, you will need the unique HEC endpoint address provided by Splunk support
For Splunk Enterprise, this will be in the form of
Please double check if SSL is enabled for HEC data inputs. If enabled, use “https” in the URI
Schedule the script to run at desired intervals in the host system