SSTA (formerly SSCM) includes SAP infrastructure monitoring and business data in Splunk enterprise operational intelligence analytics (both on-premise and cloud versions of SAP) alongside with other enterprise components.
Connects multiple SAP Solution Managers with Splunk instance.
Ability to connect to SolMan instances with granted permissions (See Configuration and SAP Prerequisites sections).
Discovers each SAP Solution Manager metrics and adds the data into Splunk monitoring.
Customization of usage of existing metrics by including meaningful or excluding less important details from the monitoring.
Ingests monitoring metrics into Splunk ITSI (Enterprise version only).
All the metrics chosen for ingestion will be instantly shown up on ITSI side. Predefined SAP metrics will be appropriately interpreted on ITSI side.
Copyright 2020 EPAM Systems.
Upcoming Version 2.0.0
WARNING - Breaking changes in upcoming version 2.0:
- Completely switching from PySlet to Requests-based ODATA client implementation. Changed state from experimental to stable
- Splunk ITSI support is going to be dropped from SSTA Community and moved to SSTA Enterprise as a feature
- Allowing a limited number of SAP SolMan enabled metrics to ingest into Splunk
Contact information for asking questions and reporting issues:
Download the SSTA application from Splunkbase - https://splunkbase.splunk.com/app/4301/
Before deploying the app, you must ensure the following:
You have activated the required OData Service AI_SYSMON_OVERVIEW_SRV and SAPUI5 application service SM_TM_SYSMON according to App Implementation: Monitor Systems - SAP Help Portal.
Authorization settings are required to be set in SAP Solution Manager and to fetch data using relevant OData service. Authorizations were described in Security Guide for SAP Fiori Apps – SAP Solution Manager 7.2 SPS8 System Monitoring - SAP Help Portal.
Configuration System monitoring SAP landscape and custom metrics were described on System Monitoring 7.2 - Setup and Configuration - SCN Wiki.
Add-on requires Splunk kvstore to be operational on the instance that it is deployed on. Make sure that it is not disabled.
Add-on is designed to store obtained data within metrics index. Create a metrics index on your indexer(s) (for example called solman_metrics).
In distributed deployment option (see option 2 below), on ITSI environment, create a user that has the capabilities to create ITSI service via REST interface.
There are two options for add-on deployment: standalone ITSI server and distributed option.
Versions 1.0.0 and 1.1.0 support only the first option.
Versions 1.2.0 and above support both.
In standalone ITSI option, the add-on is installed on the same Splunk instance that also has ITSI REST interface.
Here the ITSI Splunk instance must have direct network connectivity to SAP OData interface (be within organization's security perimeter).
The first option does not work well for ITSI in Splunk Cloud or other distributed environment when ITSI instance can not or should not access SAP instances directly.
In that case, install the add-on on Splunk Heavy Forwarder that is close to SAP instances.
It will forward all collected data to the Splunk indexers and create corresponding ITSI services using ITSI REST interface.
Install the technology add-on on either ITSI instance (option 1) or on Splunk Heavy Forwarder (option 2):
Log in to Splunk and go to Apps > Manage Apps.
Click install app from file.
Upload the app package file and click upload.
Version 1.3.0 introduced initial setup page. In order to let the v1.3.0 app understand that the application has been previously configured, edit $SPLUNK_HOME/etc/apps/sap_solman_app/local/app.conf adding the following stanza:
[install] is_configured = 1
Starting with v1.3.0, the modular input instance has to be named as "main_input". Edit $SPLUNK_HOME/etc/apps/sap_solman_app/local/inputs.conf so that the stanza is called:
After these configuration preparations, proceed with application upgrade. This can be done using UI.
Once the upgrade is done, please wait for several hours to let the application learn the actual metric update intervals. This should help eliminating gray N/A values that could be present in pre-1.3 versions of the app for the metrics that are rarely updated. The more you wait, the more precise the update intervals become.
In order to apply the new threshold level logic, after upgrade, navigate to Solman Configuration Dashboard and perform the following:
This will enforce new threshold rules and update period intervals.
After installing the application, perform the initial setup
new server versionif you want to use new Odata client(Right now, this version is experimental).
Configure the metrics to be collected. On the first invocation, modular input populates solman_metrics key-value store collection discovering all the systems and metrics available on SAP Solman. On the host having the add-on deployed, go to Solman Configuration Dashboard. Click on the button corresponding to the SAP system to be configured. Click on the sliders to enable or disable metrics collection. Once done, click on green Save button. Please wait for the Solman data to refresh before it gets into Splunk index (may take several minutes).
Navigate to ITSI Service Analyzer dashboard. You will see the data from the configured system
Use the troubleshooting dashboard within the app.
By default, app logging level is set to WARN.
To increase logging verbosity, edit $SPLUNK_HOME/etc/apps/sap_solman_app/local/log.conf adding the following stanzas:
[default] log_level = DEBUG [splunklib.modularinput.script] log_level = DEBUG [sap_solman_mi] log_level = DEBUG
Project repository https://github.com/swl10/pyslet
Version number 0.7.20170805 (modified to include search feature compatibility patch)
Project repository https://github.com/flaviusmatis/simplePagination.js/
Version number 1.6
Project repository https://github.com/requirejs/text
Version number 2.0.15
Copyright 2020 EPAM Systems
Copyright 2017 Steve Lay
Copyright (c) 2004, University of Cambridge.
Copyright 2012, Flavius Matis
Copyright jQuery Foundation and other contributors
SAP, SAP Fiori are the trademarks or registered trademarks of SAP SE in Germany and in several other countries.
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.