|
Measures reported by BobiDPSvrStTest
The Dashboards Processing Server responds to Dashboard requests by processing reports and generating encapsulated page format (EPF) pages. The key benefit of EPF is that it supports page-on-demand access, so only the requested page is returned, not the entire report. This improves system performance and reduces unnecessary network traffic for large reports.
If this server is not running or is slow in processing dashboard requests, EPF pages will either not be generated at all or may take hours to be generated. As a result, report generation will take longer than normal, thereby adversely impacting user experience with dashboards. This is why, it is imperative that administrators are notified of even the slightest deviation in the availability and performance of the Dashboards Processing server. This is exactly what the BobiDPSvrStTest test does.
This test sends out email/SMS alerts to users when the Dashboards Processing server switches to an abnormal state suddenly or when it runs out of free threads for processing subsequent dashboard requests. In the process, the test makes sure that the administrator promptly addresses these issues and quickly restores normalcy.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| healthState |
Indicates the current health state of the Dashboards 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, 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 Dashboards Processing server 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 Dashboards 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. |
|