Java Application Custom JMX Check Test

The JMX checks for Java application on subaccount level is configured from the SAP BTP cockpit, the Neo console client, or with the Checks API Information published on SAP site. This means that each application started in the subaccount will immediately receive all the JMX checks configured on subaccount level in addition to the checks configured on the application level. If there is a check configured on subaccount level and a check configured on application level with one and the same name, the one on the application level has higher priority and only it will be assigned to the started application. This test monitors the JMX checks configured for Java application and reports critical issues, if any.

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.

Configurable parameters for the test
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: 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

State

Indicates the custom JMX check status of Java applications.

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value	Numeric Value
OK	0
Stable	1
Warning	2
Unstable	3
Critical	4

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the custom JMX check status of Java applications is stable.

The CRITICAL state indicates that the JMX check fails due to an error or the attribute value is above the defined CRITICAL threshold.

The WARNING state indicates that the attribute value is above the defined WARNING threshold but not above the CRITICAL threshold.

The OK state indicates that the attribute has recovered from CRITICAL/WARNING state or it is not above the WARNING threshold.

The detailed diagnosis of this measure provides the java application custom JMX check details like timestamp, value, units and message.