eG Monitoring
 

Measures reported by CogBatReportTest

The batch report service is responsible for the execution of batch reports baseReport class. This service is dedicated to running non-interactive batch reports. For example, when a report runs as part of an agent or job or runs in the background, the request is sent to the batch report service. A report runs in the background when it is scheduled, emailed, printed, saved, or run, in response to an external occurrence. If the requests to the batch report service fail, the batch reports could not be executed at the scheduled time. Eventually, the reports scheduled will not be generated / printed / emailed, thus affecting the business of the organization. To proactively avoid failure of the requests to the batch report service, administrators can periodically execute the CogBatReportTest.

This test monitors the batch report service and reports the current status of the service. This test helps administrators identify the maximum number of processes that can be used by the dispatcher to handle requests. The maximum / minimum number of processes that were running at a give point in time since the service was last restarted helps administrators identify the load on the service. The request processing ability of the service is periodically monitored so that administrators can initiate troubleshooting at the earliest when there is a sudden / gradual increase in the count of failed requests.

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.
configuredProcesses Indicates the maximum number of processes that the dispatcher can use to handle requests from the batch report service. Number

There can be multiple report service and batch report service processes on each dispatcher. This measure displays the value that is configured against the following:

Maximum number of processes for the <service_name> during peak period and

Maximum number of processes for the <service_name> during non-peak period.

Here, <service_name> corresponds to batch report service.
processes Indicates the number of processes that are currently running. Number

A high value for this measure indicates that the service is overloaded.
processesHighWatermark Indicates the maximum number of processes that were running at a given point of time since the service was last restarted. Number

A value close to Configured Processes measure indicates that there are few / no processes that can be used by the dispatcher to handle requests.
processesLowWatermark Indicates the minimum number of processes that were running at a given point of time since the service was last restarted. Number

 
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 requests that were processed successfully during the last measurement period. Percent

Ideally, the value of this measure should be close to 100.
failedRequests Indicates the number of service requests that failed during the last measurement period. Number

A high value is a cause of concern. Administrators can analyze the reason behind why the requests are failing frequently and can initiate troubleshooting at the earliest.
failedRequestsPerc Indicates the percentage of requests that failed during the last measurement period. Percent

A value close to 0 is desirable. A sudden / gradual increase in the value of this measure warrants administrators to initiate troubleshooting at the earliest.
successfulRequestsPerSec Indicates the rate at which the requests were processed successfully during the last measurement period. Requests/Sec