Configure Monitoring Profiles

The monitoring profile determines which metric families are collected for all devices in associated device collections and how often polling occurs. The metric families in the monitoring profiles determine which components are added to the system for devices in assigned device collections and which metrics are collected for those components.
The monitoring profile determines which metric families are collected for all devices in associated device collections and how often polling occurs. The metric families in the monitoring profiles determine which components are added to the system for devices in assigned device collections and which metrics are collected for those components.
Monitoring profiles are global across all tenants.
The relationship of monitoring profiles to device collections governs monitoring. Monitoring can be triggered in the following ways:
  • A monitoring profile is associated with a device collection.
  • A device is added to a device collection that has an associated monitoring profile.
  • A metric family is added to a monitoring profile with an associated device collection. 
  • A new vendor certification is added for an existing metric family that is polled in a monitoring profile.
  • The vendor certification priority changes for a metric family.
  • A change occurs on a device. If 
    Automatically Update Metric Families
    is selected, the change to monitoring occurs automatically according to the change detection rate. If 
    Automatically Update Metric Families
    is not selected, the change to monitoring occurs when you click
    Update Metric Family
    on the Polled Metric Families tab of the Monitored Devices view.
Monitoring Profile Best Practices
Consider the following best practices for creating monitoring profiles:
  • Before you configure monitoring profiles, see Determine Monitoring Requirements.
  • Copy default monitoring profiles to create customer-specific monitoring profiles. Remove the collections that are applied to the default monitoring profiles. This model makes it easier to customize and manage device polling.
    Do not modify the DA Health Fast, Normal, and Slow monitoring profiles. These profiles are used for self-monitoring of the
    CA Performance Management
  • For monitoring flexibility, use multiple monitoring profiles. Do not add all metric families that you monitor in your network to a single monitoring profile.
  • Some metric families, such as CPU and Memory, apply broadly to all devices. You can apply a monitoring profile with these metric families to all-encompassing collections, such as All Routers or All Managed Devices.
  • Monitoring profiles control the poll rate. To poll the same metric family on different devices at different rates, create monitoring profiles with different poll rates. Apply the faster poll rate to a collection that includes only the devices that require fast polling.
  • Monitoring profiles control filtering. If different filtering criteria is required for different sets of devices, create a monitoring profile for each set of requirements.
  • Apply only metric families that are applicable to the items in the associated collections. For example, do not apply a monitoring profile that contains the VMWare metric families to a collection of routers. Unnecessary metrics add processing to the Data Aggregator at every change detection period.
Create Monitoring Profiles
To specify which metrics to gather from which devices and components, create monitoring profiles. For example, create a custom Systems monitoring profile and configure the profile to poll resource utilization counters only from SNMP.
Monitoring profiles are available in all tenant work spaces. For example, create a "Service Router Monitoring" monitoring profile and use the profile for all tenants. You do not have to create a
"Service Router Monitoring" monitoring profile for each tenant. Device collections that are associated with the monitoring profiles are tenant-scoped.
To create basic monitoring profiles, copy the out of the box monitoring profiles. Custom profiles provide flexibility.
Only Administrator users in the default tenant can modify monitoring profiles. In an MSP environment, all changes to monitoring profiles apply to all tenants.
Follow these steps:
  1. Go to
    , and click the Data Aggregator data source.
  2. Expand
    Monitoring Configuration
    , and click
    Monitoring Profiles
  3. Click
    To use an existing profile as a template, select the profile, and click
    . The copy function does not copy event rules.
  4. Specify a unique profile name and description.
  5. Select a poll rate.
    • Polling occurs at the fastest rate for all the monitoring profiles that are associated with a device collection.
    • Changes to the poll rate take up to two cycles to apply.
    • When you use the 60-minute rate for an existing device, a No Data To Display message appears in views with a time range of Last Hour. If you change the dashboard setting to a prior hour, you can see earlier data. However, the view does not display the latest data until the new poll cycle completes.
      One-minute polling on large device collections or devices with many components can affect the performance of the system.
        To poll critical interfaces at a faster rate, use a separate monitoring profile with a filter. For more information, see Poll Critical Interfaces Faster than Non-critical Interfaces.
  6. (Optional) To detect when the components on a device change, select
    Enable Change Detection
    . This option is enabled by default. If you select this option, configure the behavior:
    • Specify the change detection rate. The change detection rate determines how often the system identifies changes to component items on monitored devices. If a device is associated with multiple monitoring profiles, change detection occurs as the fastest specified rate. To determine the configuration changes,
      CA Performance Management
      uses reconciliation algorithm that is defined in the metric family.
      Consider how frequently the monitored components on the devices are likely to change. Avoid setting change detection rates that are more frequent than necessary. Some metrics, such as availability, never or rarely change. Because change detection uses some system resources, do not enable change detection for such metrics.
    • (Optional) To automatically start monitoring newly detected components, select
      Automatically Update Metric Families
      . To manually control when changes to monitoring occur, clear this option.
      If you clear this option, the system does not automatically apply changes to monitoring. The Events Display dashboard displays configuration events for the detected changes. To apply the changes to the devices, go to the Data Aggregator administration menu, Monitored Devices, and open the Polled Metric Families tab. Select the appropriate metric family, and click Update Metric Family.
       When monitoring changes are applied to devices, components that are no longer detected on the devices are marked "Not Present".
  7. Assign metric families to the
    Selected Metric Families
    By default, all metrics in each selected metric family are collected. To select a limited set of metrics, see Configure Metric Filtering.
  8. Click
    The monitoring profile is applied to any assigned collections during the next poll cycle. To start monitoring with a new monitoring profile, assign the profile to device collections.
Add Event Rules to Monitoring Profiles
Event rules set conditions to trigger Threshold Violation events. Each rule is based on a single metric family and contains criteria to raise or clear the violation. The event rules apply to each component on all devices in collections that are assigned to the monitoring profile.
You cannot add event rules to factory monitoring profiles. Only Administrator users in the default tenant can modify event rules on monitoring profiles.
For best performance and granular control, configure event rules on threshold profiles instead of monitoring profiles. For more information, see Configure Threshold Profiles.
Follow these steps:
  1. Select a custom monitoring profile.
  2. Click the
    Event Rules
  3. Click
    to create a rule, or click
    to modify an existing rule.
    For detailed information about creating event rules, see Configure Threshold Profiles.
    Events are raised and cleared when the devices in associated collections satisfy the event rule conditions.
Configure Monitoring Profile Filters
Monitoring profile filters specify criteria that governs which components are monitored. Only the component items that match the filter criteria are polled for the associated metric family. Filtering limits SNMP traffic and ensures that the system monitors only relevant components. The filters of each monitoring profile are assessed independently. 
CA Performance Management
 monitors device components if any of the monitored components pass the filter criteria of any associated monitoring profile.
Monitoring profile filters
apply after discovery. The system creates the component items but does not send SNMP requests to monitor the items. Monitored components are reassessed according to the change detection interval.
Vendor certification filters
prevent the creation of component items that do not match the filter criteria. Vendor certification filters might not recognize changes at the component level. Both filter types reduce SNMP traffic to the same level. Use vendor certification filters only when the monitoring profile filter cannot filter component item.
Example: Multi-Rate Polling
You want to monitor all interfaces with 5-minute polling, and one type of interface with 1-minute polling. One monitoring profile has a poll rate of 5 minutes. This monitoring profile is associated with a device collection. A second monitoring profile has a poll rate of 1 minute. The interface metric family on that profile has a filter that specifies the type of interface to poll at a 1-minute interval. This monitoring profile is also associated with the same device collection. 
CA Performance Management
 polls the specified interface type at a 1-minute rate and all other interfaces at a 5-minute rate.
Example: How and When Filters Are Combined
You want to apply multiple filter profiles to multiple devices. You want to exclude an attribute from one of the filters. However, the product Poll filters are not
filters. They are
filters. The product behavior is to poll as much as you can, as fast as you can. So, if two filter criteria conflict, the product
interfaces in the polling rather than
them. The following example explains how filtering works and how you can achieve your goal.
For example, you have two filters with the following configuration:
  • Filter 1
    (Description contains "Virtual-Access" or Description contains "Tunnel") 
  • Filter 2
    Name does not contain "Internal" 
This situation means that Filter 1 and Filter 2 are OR'ed. Only components that meet the previously mentioned criteria are polled.
However, if you want to
any interfaces that contain "Internal" in the Name attribute, add that filter criteria to each monitoring profile as an AND. Filter 1 should appear as follows:
  • Filter 1
    (Description contains "Virtual-Access" or Description contains "Tunnel") AND (Name does not contain "Internal)
When you have the same devices that are associated to two monitoring profiles, the two profiles must have filter criteria. In this scenario, effectively, you combine the two filters by stating exclusion criteria in both. Otherwise, the monitoring profile without the filter causes all components on the device to be polled. Therefore, Filter 2 should appear as follows:
  • Filter 2:
    (Description contains "Virtual-Access" or Description contains "Tunnel") AND (Name does not contain "Internal)
Configure Profile Filters
Only Administrator users in the default tenant can add or edit monitoring profile filters.
Follow these steps:
  1. Select a custom monitoring profile.
  2. In the Metric Families tab, select a metric family.
  3. Click
    Edit Filter
  4. Click the existing AND condition, then click a logic button, such as New AND or New OR.
  5. Select an attribute and an operation, and specify a value for the filter condition.
  6. Click
    Add Condition
  7. Create all required filter conditions.
  8. Click the
    The filter applies to the selected metric family on the next poll cycle.
    When you view metric families the assigned filters, an asterisk (*) appears next to each metric family that does not have any assigned filters.
To clear a filter, select the metric family, and click
Clear Filter
. The filter is removed on the next poll cycle. 
Associate Monitoring Profiles and Collections
To apply the polling behavior of a monitoring profile to devices, associate the profile with a device collection. When multiple monitoring profiles are associated with a device collection, Data Aggregator uses the fastest specified poll rate.
Do not associate monitoring profiles with the All Devices device collection. Doing so can cause extra SNMP requests being made to pingable-only devices, and can result in sporadic metric family support.
Metric families such as QoS, MPLS, and various Response Path Test metric families can contribute to significant SNMP requests. For more information about the implications and restrictions of SNMP requests to your network devices, see the vendor documentation or contact the vendor.
Administrators and Tenant Administrators can modify associations between monitoring profiles and device collections. Administrators see only the associated device collections for the current tenant.
Assign Collections to Monitoring Profiles
Follow these steps:
  1. From the
    Monitoring Profiles
    page, select the monitoring profile, and click the
  2. Click
  3. Select collections for the
    Assigned Collections
    list, and click Save.
    The monitoring behavior that is defined in the monitoring profile is applied to the assigned device collections.
Assign Monitoring Profiles to Collections
Follow these steps:
  1. From the
    page, select a collection, and click the
    Monitoring Profiles 
  2. Click
  3. Select monitoring profiles for the
    Assigned Monitoring Profiles
    list, and click
    The monitoring behavior that is defined in assigned monitoring profiles is applied to the device collection.
Factory Monitoring Profiles
Factory monitoring profiles let you start monitoring devices in the environment quickly. Factory monitoring profiles are automatically associated with factory device collections. For example, the Router monitoring profile is associated with the All Routers device collection.
You cannot edit or delete factory monitoring profiles.
The following factory monitoring profiles can have a significant performance impact: 
  • CBQoS
  • MPLS
  • Network Interface
  • Response Path