This test monitors the overall CPU utilization of the SAP HANA database server and reveals where the maximum CPU time is spent - in serving user requests? in system-level processing? in waiting for I/O? or being idle? This way, the test not only points administrators to the excessive CPU usage by the SAP HANA server, but also indicates the reason for the same, so that administrators can initiate the correct remedial measures.

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

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

• 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:

  create user <username> password <password>
  grant monitoring to <username>

  A sample script for user creation is:

  create user sapegadmin password eGurkha@123;
  grant monitoring to sapegadmin;

  The name of this user has to be specified in the USER text box.

• Specify the password of the specified USER in the PASSWORD text box.

  Note:

  The password should be alpha-numeric containing atleast one uppercase alphabet and a special character.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• If the value chosen for the ISPASSIVE 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.

• Once the necessary values have been entered, clicking on the Update button will 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.