Default Parameters for HanaSavPntTest

This test monitors the savepoint operation in the SAP HANA database server and reports the size of asynchronously flushed pages and row store pages during page flush and critical state. Inaddition this test also reports the maximum duration of critical phase and blocking phase. This way administrators can identify any increase in critical phase duration and promptly resolve the issue before it adversly affect the server performance.

This page depicts the default parameters that need to be configured for the HanaSavPntTest test.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the IP address of the target server that is being monitored.

• In order to monitor a SAP HANA database server, a special database user account with Monitoring privileges has to be created in every SAP HANA database instance that requires monitoring. The syntax of the script that is used for user creation is discussed in Pre-requisites for Monitoring the SAP HANA Database Server.

  The name of such a USER has to be specified here.

• Enter the password of the specified User in the PASSWORD text box and confirm it by retyping in the CONFIRM PASSWORD text box.

• In the ISPASSIVE flag, if the value chosen for this parameter is Yes, then the SAP HANA database server under consideration is a passive server in a SAP HANA cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

• By default, the detailed diagnosis of this test, if enabled, will report only the top-10 tables. This is why, the DD ROW COUNT parameter is set to 10 by default. If you want to include more or less tables in detailed diagnosis, then change the value of this parameter accordingly.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.