|
Measures reported by BobiAPSStTest
The Adaptive Processing Server (APS) is a “generic” server that processes non-Object / post-processing requests. It hosts a lot of the BI services. Multiple APSes may be defined on multiple nodes within a deployment. In almost all cases more than one APS will be needed in the system, both for management and maintenance of the running services.
If the APS fails, experiences errors, or is unable to process requests as quickly as they are received, the services it hosts will not be able to function properly, thus impacting user productivity. To prevent this outcome, administrators must rapidly detect issues affecting the health, status, and processing ability of the APS, and swiftly initiate measures to resolve them. This can be achieved with the help of the BobiAPSStTest test.
This test keeps tabs on the health, status, and processing ability of the APS, and warns administrators of impending dangers to the availability and overall performance of the server.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| healthState |
Indicates the current health state of the Adaptive Processing server in the monitored node. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| Danger |
0 |
| Caution |
1 |
| Healthy |
2 |
If the server is not healthy, then the detailed diagnosis of this measure, if enabled, provides the process ID, JVM debug information, trace flags, JVM version and service hosted by the server.
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the health state of the server. In the graph of this measure however, the same is represented using the numeric values only. |
| serverRunningState |
Indicates the current running state of the Adaptive Processing server. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| STOPPED |
0 |
| STARTING |
1 |
| INITIALIZING |
2 |
| RUNNING |
3 |
| STOPPING |
4 |
| FAILED |
5 |
| RUNNING_WITH_ERRORS |
6 |
| RUNNING_WITH_WARNINGS |
7 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the running state of the server. In the graph of this measure however, the same is represented using the numeric values only. |
| serverEnabledState |
Indicates whether/not the Adaptive Processing server is enabled. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| Disabled |
0 |
| Enabled |
1 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate whether/not the server is enabled. In the graph of this measure however, the same is represented using the numeric values only. |
| busyServerThreads |
Indicates the number of server threads that are currently servicing requests. |
Number |
If this measure reaches the configured maximum thread pool size for the server, new requests to the server would have to wait until a server thread becomes free. If this happens often, it may significantly slowdown request processing by the server. In such a situation, you may want to consider resizing the thread pool. |
|