Page Comparison

...

1. If filtering is possible, how can this filter provided to all SAP systems? 

   1. The filter needs to be setup in each system, however it can be setup in 1 system, and exported (as can all the config) and imported to a 2^nd system meaning it only has to be setup once (it comes out of the box with default setup / configuration which can be adjusted) and then exported so it can be imported in to subsequent systems. There is functionality planned for SP4 or SP5 (due Q1 CY2021) to allow central configuration to be setup and pulled down to each system automatically.

2. Which authorizations are required for data collection?

   1. There is a standard SAP role we provide that can be imported in to your SAP system can contains all of the required permissions for the PowerConnect batch job. You can import this in to a development system and examine it. 

3. How is the data transferred and stored in Splunk?

   1. Data is collected by ABAP code, and sent direct to Splunk from SAP, in json format. When it arrives in Splunk it is stored in an index, which Splunk holds on disk in the indexer. 

4. Are there any implications or issues with interruptions with users when installing PowerConnect in a production system?

   1. No user interruptions. It is regular SAINT add-on install, which is performed in 000 client. Moreover PowerConnect is fully custom, so does not require users to stop their activities. 

5. Which SAP transaction codes can PowerConnect access?

   1. PowerConnect has over 200+ extractors available out-of-the-box for the SAP ABAP system. Additionally, PowerConnect contains an extensible framework which allows it to collect information from any table within the SAP environment.

6. How often does PowerConnect pull the various transaction codes?

   1. By default data is extracted between 30-86400 seconds depending on the transaction, but this can be customized within the administrative console to meet the user’s preference.

7. Can PowerConnect access custom applications and SAP tables?

   1. Yes, it can. There is an extensible framework which allows PowerConnect to extract data from any table within the SAP system, including Z tables.

8. How long does PowerConnect keep the data?

   1. PowerConnect stores data within the SAP system for as little as one day for troubleshooting purposes. Once the data is sent to Splunk it can be stored as long as the user would like.

9. What happens if the connectivity to the Splunk System becomes unavailable?

   1. The data is stored in SAP temporarily if there is an issue connecting to Splunk, and it is sent once connectivity to Splunk is re-stablished. This data is kept by default 1 day, but can be kept longer if needed, once the data is sent to Splunk it is deleted from temporary storage. The best way to mitigate this problem is to set up alerting to see if data is not being sent to Splunk for a specific period of time.

10. How does PowerConnect retrieve OS statistics?

    1. OS statistics are obtained from the ST06 transaction code. Customers can also use Splunk collectd to obtain additional information from the OS.

11. Can PowerConnect run a custom job on the SAP system and collect the output?

    1. We can execute a custom batch job and grab the output of the batch job SM37 logs, and the output of the ABAP and send it to Splunk. We can also execute any ABAP code the customer has, but it requires a wrapper around the code to allow it to interface with PowerConnect.

12. Is PowerConnect able to access the SAP-GUI data like network latency or response time?

    1. Response time is stored in the STAD transaction which is collected by the PowerConnect application. For network data there is a RUM monitor for network traffic with a geo heat map as a standard dashboard.

13. Can PowerConnect send certain transaction codes in real time and others in batch mode?

    1. PowerConnect sends data in near-real time to Splunk. By default transactions are collected between 30-86400 seconds after installation depending on the type of transaction. This can be customized to meet user’s desired data extraction frequency in the PowerConnect administrative console.

14. Are there capabilities to limit the number of work processes that PowerConnect will consume at any one time?

    1. It is possible to limit the count of /BNWVS/DISTRIBUTE_PARALLEL jobs and count of DIA processes spawn by /BNWVS/BC_DATA_EXTRACT.

15. Are there capabilities to limit the PowerConnect work processes to a specific app server?

    1. It is possible to define a specific app server for batch jobs in Administrator->Setup Global config. DIA WPs can be targeted by setting RFC_GROUP parameter in the Global config (group should be created in advance).

16. What are limitations of PowerConnect in SAP Private Cloud?

    1. Unlike the SAP HEC Environment, there are no limitations for SAP Private Cloud at current stage. Regular S/4HANA packages could be installed in this environment.

17. Are the PowerConnect jobs expected to run for an extended period of time?

    1. Long running PowerConnect jobs is normal behavior. These jobs run for a defined interval then they restart themselves. This interval can be defined, it defaults to 1 day (86,400 sec or close to this) before they restart. This is normal, they spend most of their time asleep not doing anything, so while in this state they consume no resources. The max runtime value is defined in seconds. In theory, you could enter any valid number here, however, please take into account that there is a performance overhead (to load necessary configs, buffers, etc) and delay to start the job itself, which might impact on the metric uploading/extraction. Thus it is a matter of balance to find the maximum value which will not trigger any alerts and at the same time will not slow down the metric extraction/uploading. Our recommendation is to maintain the value of 1 day (86,400 sec), which is the default value.

18. Is it to be expected that PowerConnect will always consume two BTC work processes for collector/uploader, plus another (briefly) every 5 min for the check job.

    1. Yes, it is expected behavior (please see the table below). We need some jobs running continuously to collect/send metrics.

18. Can the PowerConnect extract and load background job runtime be reduced from its default setting of One day ( 86400 Seconds ) ?

...