Java Application CPU Load Test
Often excess CPU usage in Java application can impose a prohibitive load on the application, choking the CPU and hence making it a bottleneck. Using this test, administrators can figure out the current CPU utilization for Java application thus enabling them to take remedial actions immediately if the application is found to utilize the CPU resources excessively.
Target of the test : A SAP BTP Neo Environment
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each Java Application in the target SAP BTP Neo Environment.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
Host name of the server for which the test is to be configured. |
PortNo |
Enter the port to which the specified host listens. By default, this is 10002. |
Subaccount |
In SAP Cloud Platform Cockpit, one user account will have multiple subaccounts. So you can mention any one of the subaccount name in the Subaccount text box. To know how to determine the Subaccount, refer to Identifying the API Endpoint URL and Subaccount topic in Pre-requisites for Monitoring SAP BTP Neo Environment. |
User |
For collecting the metrics, specify the Username in the User text box. The Username here refers to the Client ID created in SAP Cloud Platform Cockpit. To know how to create such a user (Client ID) in SAP Cloud Platform Cockpit, refer to Registering the eG Agent as an API Client topic in Pre-requisites for Monitoring SAP BTP Neo Environment. |
Password |
Specify the password in the Password text box. The Password here refers to the Client Secret created in SAP Cloud Platform Cockpit. To know how to create Password (Client Secret) in SAP Cloud Platform Cockpit, refer to refer to Registering the eG Agent as an API Client topic in Pre-requisites for Monitoring SAP BTP Neo Environment. |
Confirm Password |
Confirm the password by retyping it here in the Confirm Password text box. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency. |
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:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
CPU Load |
Indicates the current CPU load for Java application. |
Percentage |
A very high value could indicate a CPU bottleneck in accessing the Java application. |