There are times when you need to gain insight into what reports are run the most in an environment, or how many reports are being run during a specific time period. With the tools in the Performance bundle of MetaManager™, we can provide that insight for you. All you need is your audit database configured in IBM Cognos and the MetaManager™ Validate module.
To start, you are going to have the Cognos audit database. To do this, you can select the "Create a connection" option from the gateway selection drop down. Alternatively, you can use the Tools context menu and select "Options". From there, you will need to click on the IBM Cognos BI tab and you can modify the connection to set up the audit database. Once you have the audit database information added to your connection you can move on to the next part.
For the next step you will need to navigate to the Validate module under the Performance bundle. You will see that there are four different audits reports that can be run. We will focus on the Reports Audit report. In order to use this audit you will need to click on the "Reports Audit" to load that specific audit and then select your time frame from the drop down. You can do as little as 30 minutes ago up to 30 days ago.
You can see from the image below that there were a large number of reports that were run over the last 4 hours. The status column indicated whether or not the report ran successfully or failed. There seems to be a significant mix of both successful runs and failed runs over this time period.
If you want to focus just on the report failures, you can do so by checking the "Show Failures Only" checkbox and re-running the audit.
We can click on the failed report runs as well and that will show us the error. You can see from the error message that these reports are failing because of a parsing error and that the data item listed is not available in the model. This insight can help me take corrective action before more reports will fail. We can use the export function to save the results as an Excel file by clicking "Export...". We can do further processing from here, such as filtering on the exception to see if there are other reports that have the same error.