Deployment Guide › iConsole Standard Searches, Reports and Policies › Dashboard Data Aggregation › Configurable Aggregation Parameters

Configurable Aggregation Parameters

For both SQL Server and Oracle CMSs, you can customize the following aggregation parameters:

Timeslot length

Also known as 'timeslot granularity', this is the number of minutes for each timeslot in the aggregation. The default length is 60 minutes. This means, for example, that the number of blocked emails or disregarded Warnings are aggregated over consecutive 60 minute periods. The minimum timeslot length is 30 minutes. Be aware that shorter timeslots ('higher granularity') require more DBMS storage.

Start date

This metric specifies the start date and time for the initial aggregation. Incidents with a capture timestamp after this start date are included in the aggregation. The start date defaults to midnight on the first day of the current month, but you can change it to any date or time.

Purge existing data

You can optionally purge all existing aggregated data from the database, and replace it with data re-aggregated from a new start date.

Data age

This specifies the maximum age for data in the aggregation tables. This parameter enables you to regularly purge database tables containing the aggregated incident data used to generate the dashboard charts and metrics.

Escalated Events metric

By default, this metric only counts incidents with a value of 'Escalate' in the Audit Status field. But you can change this definition so the metric only counts incidents with some other combination of values in these audit fields.

Reviewed Events metric

This metric calculates the total number of incidents that have been reviewed over the period.

By default, this count only includes incidents with one or more values set in the Audit Status, Action Taken or Resolution audit field. The presence of any value in these audit fields is taken as confirmation that the incident has been audited by a reviewer. But you can narrow the metric definition to only include incidents with specific values in these audit fields.

Note: New incidents are defined as incidents with no associated issues. You cannot customize the 'New Events' metric.

Root policy node

By default, aggregation jobs include incidents associated with any predefined or custom policy. But you can use this parameter to customize aggregation jobs to only include incidents associated with specific policies.

Frequency

By default, aggregation jobs run every hour. Although there is no job parameter to configure this, you can specify how often aggregation jobs run by editing the SQL Server job directly or by running an Oracle PL/SQL command.

More information:

Aggregation Parameters