|
Measures reported by BobiConnSvrTest
The Connection Server provides database access to source data. It supports relational databases, as well as OLAP and other formats. The Connection Server is responsible for handling connection and interaction with the various data sources and providing a common feature set to clients. Without the connection server therefore, source data cannot be accessed, thereby causing critical services to fail. Moreover, if the connection server slows down, so will database accesses. To avoid such failures/slowdowns, administrators should run the BobiConnSvrTest test at regular intervals, check the status of the connection server, determine whether/not the server is sized right to process its current and future request load, and in the process, promptly detect a server failure or slowness. Quick and accurate problem identification will enable administrators to swiftly initiate corrective action, so that the Connection server resumes normal operations in no time.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| healthState |
Indicates the current health state of the Connection 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, will provide the process ID of 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 Connection 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 Connection 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. |
|