HANA XS Application Instances Test

This test monitors all the applications deployed on the specified space in the target organization of SAP HANA XS Advanced system and reports the total number and the uptime of the application instances. This test also reveals the number of instances that are currently starting, running, crashed and stopped. This way, the test alerts the administrators when any applications instances are crashed or stopped and thereby helping them to react proactively and remediate application instance crashes before it negatively affects the performance.

Target of the test : A SAP HANA XS advanced Application server

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the combination of space:buildpack:application on the target server being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port number at which the specified Host listens to. By default, this will be 30015.
Organization	Specify the name of the Organization that contains the spaces in which the applications are deployed on HANA XS in this text box. Example: org
Spaces	Specify a comma-separated list of Spaces for the specified Organization in HANA XS in this text box. The Spaces specified in this text box need to be included for monitoring. Example: SAP,PROD
XS Path	Specify the full path to the location where the HANA XS is installed in this text box. Example: /HANA/shared/HDB/xs/bin/
CLI User	Typically, to connect to a HANA XS and run tests, the eG agent requires the permissions of a HANA XS client user who has been assigned the role collections as XS_CONTROLLER_ADMIN_READ_ONLY, also assigned the OrgAuditor, SpaceAuditor roles for specified organization and spaces. Ideally, you will have to create a new user role on the HANA XS for this purpose, associate the above-mentioned collections with that role, and assign the new role to an existing HANA XS client user. Once the new role is assigned to a HANA XS client user, specify the name of this user against CLI User text box. Example: To create user as XSA_ADMIN2. Execute below query in SAP HANA studio. CREATE USER XSA_ADMIN2 PASSWORD “admin”; Assign roles for HANA XS CLI user using HANA XS Client commands mentioned below: xs assign-role-collection XS_CONTROLLER_ADMIN_READ_ONLY XSA_ADMIN2; xs set-org-role XSA_ADMIN2 orgname OrgAuditor; xs set-space-role XSA_ADMIN2 SAP SpaceAuditor;
CLI Password	Specify the password of the specified CLI User in this text box.
Confirm Password	Confirm the password by retyping it in this text box.
CLI Location	The XS CLI client tools are installed by default on the SAP HANA server. However, you can also download and install the client tools locally, if you want to connect to SAP HANA from your local machine. Hence, set this flag to Remote or Local based on the location of HANA XS Client.
CLI Endpoint	Specify the URL of the API end point to connect to the XS advanced controller on the SAP HANA server in this text box. Syntax for this CLI endpoint is : https://<Hostname>: 3<Instance Number>30. Example: https://vhcalhdbdb.dummy.nodomain:30030.
Include Applications	Specify a comma-separated list of destination patterns that need to be included for monitoring in this text box. Example:hrtt-service,hrtt-core. By default, this parameter is set to Few Applications.
Exclude Applications	Specify a comma-separated list of destination patterns that need to be excluded for monitoring in this text box. Example:hrtt-service,hrtt-core. By default, this parameter is set to None.
Monitoring Java Apps	By default, this flag is set to No. This means that by default, this test does not monitor Java Applications. Set this flag to Yes if you want to monitor the Java Applications.
Monitoring NodeJS Apps	By default, this flag is set to No. This means that by default, this test does not monitor NodeJS Applications. Set this flag to Yes if you want to monitor the NodeJS Applications.
Monitoring Python Apps	By default, this flag is set to No. This means that by default, this test does not monitor Python Applications. Set this flag to Yes if you want to monitor the Python Applications.
Monitoring PHP Apps	By default, this flag is set to No. This means that by default, this test does not monitor PHP Applications. Set this flag to Yes if you want to monitor the PHP Applications.
Monitoring Ruby Apps	By default, this flag is set to No. This means that by default, this test does not monitor Ruby Applications. Set this flag to Yes if you want to monitor the Ruby Applications.
Monitoring Other Apps	By default, this flag is set to No. This means that by default, this test does not monitor Other Language Applications. Set this flag to Yes if you want to monitor the Other Language.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Weighted instance uptime	Indicates the percentage of time this application instance has been up.	Percent
Total instances	Indicates the total number of instances currently available for this application.	Number
Running instances	Indicates the number of instances of this application that are currently running.	Number	The application instance started successfully and is accessible.
Starting instances	Indicates the number of instances of this application that are currently in starting state.	Number	The application instance has started, for example, at the request of an administrator, but is not yet accessible.
Crashed instances	Indicates the number of instances of this application that are crashed.	Number	The application instance terminated unexpectedly. Use the detailed diagnosis of this measure to know the Index no, Created time, Host, Internal port, OS User, and Failure reason of the application instances.
Stopped instances	Indicates the number of instances of this application that are stopped.	Number	The application instance stopped, for example, at the request of an administrator, and is not accessible.