Group Aggregate Trend Report

The Group Aggregate Trend (GAT) report aggregates data for a group of managed items for a specified period time. For example, you can generate a report that includes bits per second in for a group of interfaces in the previous month. The report provides this following data for up to four metrics:
capm360
The Group Aggregate Trend (GAT) report aggregates data for a group of managed items for a specified period time. For example, you can generate a report that includes
bits per second in
for a group of interfaces in the previous month. The report provides this following data for up to four metrics:
  • Number of items in the group
  • The number reflects the count of active devices or components. The report does not include a device or component in the number in the following cases:
    • Polling is disabled for an item
    • The metric has no data for the selected time period
  • Minimum value that is calculated for selected period and metric
  • Maximum value that is calculated for selected period and metric
  • 95-percentile value that is calculated for selected period and metric
  • 98-percentile value that is calculated for selected period and metric
This article includes the following topics:
Configure the GAT Report
CA Performance Management
includes the following options that you can configure to view aggregated group metrics.
  • Time Period
  • Time Zone
  • Group Name
  • Metric Family
  • Enable Variable
    x
    Select this option to add a metric to the report. You can specify up to 4 metrics.
  • Variable
    x
    Specify the metric that the report will include.
  • Rounding Pattern
  • Locale
  • Business Hours
    Specify the days that you want
    CA Performance Management
    to use in the report. Specifying business days can limit data to high-traffic times.
Understand the Time Granularity Selector
Sometimes, when a user selects a time period, the report shows data for only part of that period. For example, a report with the following settings is run on September 28:
  • Time Period:
    Previous Month
  • Time Granularity:
    As Polled
Instead of the report starting on August 1 as expected, it starts on August 14.
Group_Trend_Report_1
Group_Trend_Report_1
The report displays partial results for the time period because of the data retention settings.
CA Performance Management
uses the following default data retention settings:
  • Polled data: 45 days
  • Hourly rollup data: 90 days
  • Daily rollup data: 365 days
  • Weekly rollup data: 730 days
For more information, see Configure Data Retention Rates.
In the previous example, the report was configured to include polled data for August. However, because the report was run September 28,
CA Performance Management
only retained data from August 14 (September 28 - 45 days is August 14).
To see data for the entire month of August, change Time Granularity to Hourly. Because hourly data is retained for 90 days,
CA Performance Management
can display data for all of August.
Group_Trend_Report_2
Group_Trend_Report_2
Configure a Custom Time Period
If the default time periods do not meet your needs, you can add a new Time Period .
Follow these steps:
  1. Log in to the CABI Reports Server as a user with edit permissions.
  2. Go to
    Public/ca/Performance Management/inputcontrols/list of values
    .
  3. Edit the
    Time Periods Group
    .
  4. Add any interval that the OpenAPI supports.
  5. Specify the following information for the new time period:
    • Name
      Specify the name that appears in the Time Period options list.
    • Value
      Specify the custom timeframe.
List_of_Values
List_of_Values
Troubleshoot the GAT Report
Report Timeout
Sometimes, the GAT report fails if you specify a long Time Period (month or more),
and
As Polled
as the Time Granularity setting. The report can fail because of a timeout on the Data Aggregator. The default query timeout setting on the Data Aggregator is 30 seconds.
To resolve this issue, choose
one
of the following options:
  • Set the Time Granularity to Hourly and rerun the GAT report.
  • Increase the Data Aggregator timeout setting (defaultQueryTimeoutSecs - Default: 30)
    You can change the value of the defaultQueryTimoutSecs parameter during query execution (for current query only) or permanently in the following location:
    /opt/IMDataAggregator/apache-karaf-<vers>/etc/com.ca.im.odata.beans.ODataLimiters.cfg
    For more information, see Configure OpenAPI Defaults and Limits.
In
CA Performance Management
tests, CA Technologies found that the appropriate Data Aggregator timeout setting for 10,000 interfaces is
defaultQueryTimeoutSecs=60
. However, you may need to increase the timeout setting if there are more items in the group the report is run against.