Viewing diagnostic alerts
This topic contains the following sections:
The Diagnostic alerts page displays diagnostic information about the TrueSight Capacity Optimization platform, showing a list of diagnostic, failure, error and warning messages generated and logged by TrueSight Capacity Optimization components.
You can access this page in any of the following ways:
- Navigate to Administration > DATA WAREHOUSE > Status. In the Alerts section, click the Diagnostic Alerts link.
- Navigate to Administration > System > Diagnostic alerts.
- Click the See details or error message code links reported in the Diagnostic Alert Summary area of the Welcome page
- Click the Show diagnostic alerts page link in the Notification area of the Welcome page.
The following image shows an example of the Diagnostic alerts page.
Diagnostic alerts page
Using data display options
The Diagnostic alerts page displays a table that lists all Errors, Warnings and Failures logged by TrueSight Capacity Optimization. You can use the following options to change the way data is displayed in the table.
|Display diagnostic alerts for|
Select the time range for which to display alerts in the table. You can select any one of the following:
|Group by component and subcomponent|
Select if you want to group alerts in the table by component and subcomponent:
Select this check box to hide all closed alerts in the table.
If you clear this check box, all closed alerts are displayed in the table, and are denoted by dimmed alert icons as shown in the following image
To collect all logs from the Diagnostic alerts page, click the Collect logs button. You are redirected to the Collect logs page and TrueSight Capacity Optimization automatically begins collecting all types of log files.
The List of log files being collected table is displayed, and it contains the following information:
|Type||The type of, or name of the component for which the log file is being collected. For example, ETL task, System task, Application server.|
|Name||Name of the task associated with the component for which the log file is being collected. For example, Optimizer - daily, Hierarchy Manager.|
Status of log collection for each type:
|Progress||Live progress, in percentage, of the log collection activity.|
|Log files||Displays one or moreclickable icons that enable you to download the collected and processed log files. These icons are displayed once the collection progress is 100% complete.|
|Click the button to download all collected log files together. Logs are downloaded as a .zip file titled collectedReports.zip.|
The following image shows an example of the table:
Viewing the Diagnostic alerts table
The Diagnostic alerts table displays the following information:
Click the button to select any one of the following options:
When you close any diagnostic alert, you close that occurrence of the alert. If the issue persists, the alert is displayed again.
|Use the check box to select or clear all alert messages. This control is normally used in conjunction with the Close button.|
Depicts alerts with one of the following icons to distinguish their type:
|Last occurrence||A timestamp depicting the last occurrence of the particular alert in the system.|
|First occurrence||A timestamp depicting the first occurrence of the particular alert in the system.|
|Timestamp||The time and date on which the alert was logged in the system.|
|Occurrences||Total number of occurrences of the particular alert.|
|Error Code||The TrueSight Capacity Optimization error code associated with the type alert. For a complete listing, see Error codes.|
|Component||The TrueSight Capacity Optimization component that generated the error. Examples are: DATAHUB, SCHEDULER.|
|Subcomponent||The TrueSight Capacity Optimization subcomponent that generated the error. This is a hyper-linked Task ID of the task assciated with the component that generated the error. Clicking on it takes you to the details page for the particular task. To return to the Alerts page, use your browser's Back button.|
|Message||The text of the error message logged in the log file of the component. You can expand the message box to view full details of the error.|