Configure Monitoring Profiles
Monitoring profiles determine the metric families that a device in an associated device collection collects and how often it polls. 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 determine the metric families that a device in an associated device collection collects and how often the metric family polls. The metric families in the monitoring profiles determine which components it adds to
DX NetOps Performance Managementfor devices in assigned device collections and which metrics it collects for those components.
Monitoring profiles are global across all tenants.
In this article:
The relationship of monitoring profiles to device collections governs monitoring. Monitoring is triggered when the following occurs:
- 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 device is changed.
Monitoring Profile Best Practices
Consider the following best practices for creating monitoring profiles:
- Before you configure monitoring profiles, see Determine Monitoring Requirements.
- To make it easier to customize and manage device polling, create custom monitoring profiles by copying default monitoring profiles. Remove the device collections that have been applied to the default monitoring profiles.A built-in mechanism uses theDA Health (Fast),DA Health (Normal), andDA Health (Slow)monitoring profiles to self-monitorDX NetOps Performance Managementcomponents. Do not modify these monitoring profiles.
- 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 a Monitoring Profile
To specify which metrics to gather from which devices and components, create monitoring profiles. For example, create a custom
Systemsmonitoring profile, and then 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 Monitoringmonitoring profile and use the profile for all tenants. You do not have to create a
Service Router Monitoringmonitoring profile for each tenant. Device collections that are associated with the monitoring profiles are tenant-scoped.
You can create basic monitoring profiles by copying 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:
- Hover overAdministration,Data Sources, and then click the data aggregator data source.TheMonitored Devicespage appears.
- UnderMonitoring Configuration, clickMonitoring Profiles.TheMonitoring Profilespage appears.
- Do one of the following:
TheCreate / Edit Monitoring Profiledialog opens.
- ClickNewat the bottom of the page.
- To use an existing profile as a template, select the monitoring profile that you want to use as a template, and then clickCopy.This option does not copy event rules.
- Complete the following fields, and then clickSave:
- NameEnter a unique profile name.Required:Yes
- DescriptionEnter a unique description.
- SNMP Poll RateSelect a poll rate.Required:YesOptions:1 minute, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutesDefault:5 minutes
- Polling occurs at the fastest rate for all the monitoring profiles that are associated with a device collection.
- Changes to the poll rate can take up to two cycles to apply.
- When you use the 60-minute poll rate for an existing device, aNo Data To Displaymessage appears in views with a time range ofLast 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.
- Enable Change DetectionDefines whether to detect when the components on a device change.Default:Selected (The monitoring profile detects changes to components on devices.)When selected, configure the behavior:
- Detection RateSpecify the rate at whichDX NetOps Performance Managementidentifies changes to component items on monitored devices. If a device is associated with multiple monitoring profiles, change detection occurs as the fastest rate that you specify. To determine the configuration changes,DX NetOps Performance Managementuses the 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.
- Automatically Update Metric FamiliesDefines whether to have your monitoring profile automatically monitornewly-detectedcomponents or to manually control when changes to monitoring occur. When this option is selected, the changes to monitoring occur automatically according to theDetection Rate. If you choose to manually control when changes to monitoring occur (clear this checkbox), the changes to the device apply when you update the metric family. When the changes are applied to devices, components that are no longer detected on the devices are marked "Not Present".Default:SelectedClearing this option does not automatically apply the changes to monitoring. TheEvents Displaydashboard displays configuration events for the detected changes.To apply the changes to the device, update the metric family:
- From theMonitored Devicespage, click the device to which you want to apply the changes, and then click thePolled Metric Familiestab.
- Select the metric family that you want to update, and then clickUpdate Metric Family.TheUpdate Metric Familydialog opens.
- Select the metric families from theAvailable Metric Familiestree that you want to assign to the monitoring profile, and then click the right arrow to add it to theSelected Metric Familieslist.By default, all metrics in each selected metric family are collected. To select a limited set of metrics, see Configure Metric Filtering.
The monitoring profile is applied to the assigned collections during the next poll cycle.
Next Step:To start monitoring with this monitoring profile, assign the monitoring profile to the device collections.
Add an Event Rule to a Monitoring Profile
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 the out-of-the-box 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:
- Select a custom monitoring profile.
- Click theEvent Rulestab.
- ClickNewto create a rule, or clickEditto modify an existing rule.For more information about how to create event rules, see Configure Threshold Profiles.Events are raised and cleared when the devices in associated collections satisfy the event rule conditions.
Configure a Monitoring Profile Filter
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.
- DX NetOps Performance Managementmonitors device components if any of the monitored components pass the filter criteria of any associated monitoring profile.
- Monitoring profile filtersapply after discovery.DX NetOps Performance Managementcreates 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 filtersprevent 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 assigned to 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.
DX NetOps Performance Managementpolls the specified interface type at a 1-minute rate and all other interfaces at a 5-minute rate.
Example: How and When
DX NetOps Performance ManagementCombines Filters
You want to apply multiple filter profiles to multiple devices. You want to exclude an attribute from one of the filters. However, poll filters are not
exclusionfilters. They are
DX NetOps Performance Managementpolls as much as it can, and as fast as it can. So, if two filter criteria conflict,
DX NetOps Performance Management
includesinterfaces in the polling rather than
excludethem. 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.
DX NetOps Performance Managementpolls only the components that meet the previously mentioned criteria.
However, if you want to
excludeany 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)
Manage Profile Filters
Only Administrator users in the default tenant can manage (add or edit) monitoring profile filters.
Follow these steps:
- Select a custom monitoring profile.
- In theMetric Familiestab, select a metric family, and the clickEdit Component Filter.TheAdd / Edit Filter Expressiondialog opens.
- Do the following:
- Click the existing AND condition, then click a logic (button), such asNew ANDorNew OR.A logic is added to the AND condition.
- Select the logic, add an attribute and an operation, specify a value for the filter condition, and then clickAdd Condition.
- Create the required filter conditions for the logic.
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.
Apply Monitoring Profile Polling Behavior to Devices
To apply the polling behavior of a monitoring profile to devices, the monitoring profile must be associated with a device collection. When multiple monitoring profiles are associated with a device collection, the data aggregator uses the fastest specified poll rate.
To prevent extra SNMP requests being made to pingable-only devices, and result in sporadic metric family support, do not associate monitoring profiles with the
All Devicesdevice collection.
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 the associations between monitoring profiles and device collections. Administrators see only the associated device collections for the current tenant.
Assign Device Collections to a Monitoring Profile
Follow these steps:
- From theMonitoring Configurationsection, clickMonitoring Profiles.TheMonitoring Profilespage appears.
- Select the monitoring profile to which you want to assign device collections, and then click theCollectionstab.
- ClickManageat the bottom of the page.TheAssign Collections to Monitoring Profilesdialog opens.
- Move the device collections that you want to assign to the monitoring profile to theAssigned Collectionslist, and then clickSave.
The polling behavior that is defined in the monitoring profile is applied to the associated device collection.
Assign Monitoring Profiles to a Device Collection
Follow these steps:
- From theMonitoring Configurationsection, clickCollections.TheCollectionspage appears.
- Select the collection to which you want to assign monitoring profiles, and then, from theMonitoring Profilestab, clickManageat the bottom of the page.TheAssign Monitoring Profiles to Collectionsdialog opens.
- Move the monitoring profiles that you want to assign to the collection to theAssigned Monitoring Profileslist, and then clickSave.
The monitoring behavior that is defined in assigned monitoring profiles is applied to the device collection.
Out-of-the-box Monitoring Profiles
You can you start monitoring devices in the environment quickly using the out-of-the-box monitoring profiles. These monitoring profiles are automatically associated with the out-of-the-box device collections. For example, the
Routermonitoring profile is associated with the
All Routersdevice collection.
You cannot edit or delete the out-of-the-box monitoring profiles.
The following out-of-the-box monitoring profiles can have a significant performance impact:
- Network Interface
- Response Path