Adding report fields

Select report fields to add additional information to seasonal and related event reports, historical event reports, and instance reports.

Before you begin

If you add any custom columns to any of the reports defined in the Event Analytics Setup Wizard and define a column title for this column, then, if you want the column title to appear in a non-English language in the relevant Event Analytics report, you must edit the relevant customization files. For more information about rendering column labels in a non-English language, see http://ibm.biz/impact_trans.

If you do not do this, then when the column title is displayed in the relevant Event Analytics report, it will appear in English, regardless of the locale of the browser.

If you encounter a blank screen when you reach this page then there might be missing fields in the Historical Event Database. To resolve this issue, see the relevant section in Troubleshooting Event Analytics configuration.

Procedure

  1. Specify the Aggregate fields.

    You can add aggregate fields to the seasonal and related event reports, by applying predefined aggregate functions to selected fields from the Historical Event Database. These fields are displayed in the seasonal and related event reports in the same order as they appear as follows.

    Example: To display the maximum severity of all the events that make up a related event group select the SEVERITY field, then apply the Max aggregate function, and click Include in reports: Related.
    Note: It is highly recommended that you specify the IDENTIFIER field to include in this report. This field will of invaluable assistance in interpreting the report, as it will help you to determine the precise event identity of each of the events in the report. If you are using a different field or fields than IDENTIFIER as your default event identity, then add those fields here instead of IDENTIFIER. If, in addition to the default event identity field, you are using different fields as the event identity in any specific configuration, then add those fields here in addition to IDENTIFIER.

    Once you have saved these settings, you must rerun the relevant configuration scans in order for the changes to become visible in your seasonal and related event reports.

  2. Specify the Historical report fields.
    The fields specified here are displayed in the historical event report, in the same order as they appear as follows. The historical event report is shown when you drill in from a seasonal event to its contributing historical events.
    Note: It is highly recommended that you specify the IDENTIFIER field to include in this report. This field will of invaluable assistance in interpreting the report, as it will help you to determine the precise event identity of each of the events in the report. If you are using a different field or fields than IDENTIFIER as your default event identity, then add those fields here instead of IDENTIFIER. If, in addition to the default event identity field, you are using different fields as the event identity in any specific configuration, then add those fields here in addition to IDENTIFIER.

    When you next open the historical event report, wait 20 seconds for your changes to appear.

  3. Specify the Instance report fields.
    The fields specified here are displayed as additional fields in the instance report for a related event group, in the same order as they appear as follows. The instance report is shown when you drill into event details from a related event group, to show the instances of that group.
    Note: It is highly recommended that you specify the IDENTIFIER field to include in this report. This field will of invaluable assistance in interpreting the report, as it will help you to determine the precise event identity of each of the events in the report. If you are using a different field or fields than IDENTIFIER as your default event identity, then add those fields here instead of IDENTIFIER. If, in addition to the default event identity field, you are using different fields as the event identity in any specific configuration, then add those fields here in addition to IDENTIFIER.

    When you next open the instance event report, wait 20 seconds for your changes to appear.

  4. Click Save to save your changes.