Monitoring IBM Cognos Business Intelligence

eG Enterprise offers a specialized IBM Cognos Business Intelligence monitoring model that monitors the services offered by the target server, and proactively alerts administrators if any of the services is very poor in processing the received requests successfully.

Figure 1 : The layer model of the IBM Cognos Business Intelligence server

By continuously monitoring the IBM Cognos Business Intelligence server, administrators can accurately find out the answers the following performance questions:

  • What is the current status of the Annotation Service?
  • How many requests that the Annotation Service failed to process?
  • What is the rate at which the annotation service processed the requests successfully?
  • What is the current status of the Content Manager service?
  • How many documents were successfully imported / failed to be imported into the Content store from an external data source by the Content Manager service?
  • Is the Batch Report Service currently available? if so, how many processes were used by the dispatcher to handle requests?
  • Is the Batch Report Service overloaded with requests?
  • Is the Graphics Service available to process requests? if so, how many processes were used by the dispatcher to handle requests? is it overloaded with requests?
  • How many Human Task Service requests failed?
  • Is Job Service available? if so, how many job execution requests were successful/failed?
  • Is the Metadata Service overloaded with requests?
  • How many Query Service requests were successful/failed?
  • Is the Report Data Service available? if so, how many Report Data Service requests were successful/failed?
  • What is the current status of the Repository Service?
  • How many Event Management Service requests failed?
  • What is the current status of the Mobile Service?

The tests mapped to the Operating System, Network, TCP and Application Processes layers have already been discussed in the Monitoring Unix and Windows document in detail. The JVM layer and the tests associated with this layer have been briefly discussed in the Monitoring java Application document. To know more about the Application transactions layer and the tests pertaining to it, refer to The eG Java Business transactions document.