eG Monitoring

Measures reported by ScpAppJavaCutomTest 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. Outputs of the test :One set of results for each Java Application in the target SAP BTP Neo Environment. The measures made by this test are as follows:
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.