Home  Additional Topics > Reference Information > General Reference Information > Data Aggregation



Data Aggregation

Mercury Business Availability Center uses data aggregation to make data handling and management more efficient and to improve the speed and performance of report generation. Mercury Business Availability Center data aggregation tasks are performed on the Data Processing Server.

Mercury Business Availability Center aggregates various types of data that it collects for reports (for example, response time data collected by Business Process Monitor, infrastructure machine performance data collected by SiteScope, and user traffic data collected by Real User Monitor). Data aggregation involves combining individual measurements into manageable chunks. The result is improved speed and performance of report generation.

Categories of Data

Mercury Business Availability Center groups data into three categories:

How Data Is Aggregated

Mercury Business Availability Center aggregates data collected by Business Process Monitor, Client Monitor, and SiteScope data collectors (not including SiteScope Integration Monitors using the event data template).

You can define a different delay for when the aggregation begins in the Offline Aggregator context of the Infrastructure Settings page (Admin > Platform > Setup and Maintenance > Infrastructure Settings > Foundation > Offline Aggregator). You can specify a separate delay for Business Process Monitor, custom, and SiteScope data. The delay you specify is for both the hourly and daily aggregations. It is recommended that only advanced users change the defaults set in Infrastructure Settings and after first consulting Mercury Customer Support or your Mercury Services representative. For details on using the Infrastructure Settings page, see Infrastructure Settings in Platform Administration.

How Reports Use Aggregated Data

Whether Mercury Business Availability Center displays a report using raw data, daily aggregated data, or hourly aggregated data depends on several factors:

Note: (not relevant for Mercury Managed Services customers) The following setting can be configured in the Infrastructure Settings Manager, Foundations > Generic Data Engine context, Generic Data Engine - Aggregation table to modify the way aggregated data is used in reports (in general these settings should not be modified without first consulting Mercury Customer Support):

Aggregation Policy setting - Defines the aggregated data usage policy for reports that use custom data. By default, reports use all available data (raw and aggregated); however in certain circumstances it may be necessary to modify this setting—for example, if the aggregation engine is not working (aggregator process on the Data Processing Server is down), you could modify the setting so that only raw data is used.

Effect of Outlier Setting on Data Aggregation

When aggregating data, if the Ignore outlier data in reports setting is cleared in a profile's properties, in the Transaction Threshold Settings section, in Monitor Administration, Mercury Business Availability Center excludes transaction instances whose response time exceeds the outlier value, also set in the Transaction Threshold Settings section. If the Ignore outlier data in reports setting is selected, Mercury Business Availability Center ignores outlier transactions, and therefore the data is not considered. Note that the default outlier value for all transactions is 45 seconds. For details on configuring outlier values, see Transaction Threshold Settings in End User Management Data Collector Configuration.

Data Aggregation Limitations

The following limitations apply, as a result of data aggregation:

Data Aggregation and Service Level Management

Service Level Management aggregates data differently. For details, see Aggregated Data in Using Service Level Management.




Copyright 2006 Mercury Interactive Corporation