|
Measures reported by CogAnnotatinTest
Annotation service stores and manages comments against the context of a dashboard, report, report widget, or report element that is made accessible through IBM Cognos Workspace. These comments persist across multiple versions of a report. The annotation service also supports comments associated with tasks in My Inbox in IBM Cognos Connection. The annotation service also supports IBM Cognos Workspace features and features related to human tasks in IBM Cognos Connection when it receives requests from reportDataService. If too many requests failed, the service will not be able to fetch the comments from the IBM Cognos Workspace. As a result, administrators may not know the critical information about the features and the comments entered for the elements that are accessible through IBM Cognos Workspace. To avoid request failures, administrators should continuously keep vigil on the status and request processing capability of the annotation service. For this purpose, administrators can use the CogAnnotatinTest.
This test monitors the annotation service and reports the current status of the service. This test also throws light on the number of annotation service requests that successful/failed. This test helps administrators initiate troubleshooting to determine the reason for request failures and resolve the same at the earliest.
Outputs of the test: One set of results for the target IBM Cognos Business Intelligence suite being monitored.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| status |
Indicates the current status of the service. |
|
The values that this measure can report and their corresponding numeric values are listed in the table below:
| Measure Value |
Numeric Value |
| Available |
100 |
| Unavailable |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the service. In the graph of this measure however, the same is represented using the numeric equivalents only i.e., 0 or 100.
|
| processedRequests |
Indicates the number of requests that were processed during the last measurement period. |
Number |
|
| successfulRequests |
Indicates the number of service requests that were successful during the last measurement period. |
Number |
A high value is desired for this measure.
|
| successfulRequestsPerc |
Indicates the percentage of processed requests that were successful during the last measurement period. |
Percent |
A value close to 100 percent denotes that most of the requests were processed successfully.
|
| failedRequests |
Indicates the number of service requests that failed during the last measurement period. |
Number |
A high value is a cause of concern. Administrators must analyze why the requests are failing frequently and initiate troubleshooting measures at the earliest.
|
| failedRequestsPerc |
Indicates the percentage of processed requests that failed during the last measurement period. |
Percent |
A value close to 100 is a cause of concern. A sudden / gradual increase in the value of this measure warrants administrators to initiate troubleshooting at the earliest.
|
| successfulRequestsPerSec |
A value close to 100 is a cause of concern. A sudden / gradual increase in the value of this measure warrants administrators to initiate troubleshooting at the earliest. |
Requests/Sec |
|
|