Configure Monitoring with Profile Types

A monitoring administrator uses Monitoring Configuration Service (MCS) to create configuration profiles for devices or resources. You use the profile types that are displayed on the Monitoring tab in USM to create configuration profiles. When you save a configuration profile, the profile type and configuration profile move to the top of the middle panel of the Monitoring tab.
uimpga-ga
configure_monitoring_MCS
A monitoring administrator uses Monitoring Configuration Service (MCS) to create configuration profiles for devices or resources. You use the profile types that are displayed on the 
Monitoring
 tab in USM to create configuration profiles. When you save a configuration profile, the profile type and configuration profile move to the top of the middle panel of the 
Monitoring
 tab.
The settings that you enter on profile types are stored in configuration profiles. At periodic intervals, MCS applies the configuration profiles to the selected targets. After you create a configuration profile, continue to use MCS to manage configuration settings.
 
Content
 
 
 
Video Resources
View the 
Device Monitoring with MCS
 and the 
Group Monitoring with MCS
 videos for a brief overview of how to apply monitoring configuration to target devices in your CA UIM environment. When you upgrade to CA UIM 8.5.1, watch the 
Update MCS Templates
 
 
video to learn how to update templates with configuration profiles to newer versions.
 
Device Monitoring with MCS
: In this video, we show you how to use 
Monitoring Configuration Service
 (MCS) in CA UIM to create monitoring configuration profiles. MCS applies these profiles to target devices and deploys probes as needed.
 

 
 
Group Monitoring with MCS
: In this video, we show you how to use 
Monitoring Configuration Service
 (MCS) in CA UIM to copy a tested monitoring configuration profile to a group of devices. MCS applies the copied profile to all the devices in the group, and deploys probes as needed. 
 

 
 
Update MCS Templates
: In this video, we show you how to update templates with configuration profiles to newer versions after you upgrade to CA UIM 8.5.1.
 

 
Before You Create a Configuration Profile
Meet the following prerequisites to allow MCS to deploy probes and configuration profiles to target devices or resources:
  • Install robots on the target devices.
  • Verify that the probes you can configure and deploy with MCS are in the local archive on the hub file system. When probes are not in the archive, you cannot use the corresponding profile type on the 
    Monitoring
     tab to create configuration profiles.
  • Verify that all the probe licenses are up to date.
  • (CA UIM 8.4 to CA UIM 8.5) Select a 
    device model 
    for each USM group. A 
    device model 
    is required for a group before you create or copy a group configuration profile.
Using Profile Types
A monitoring administrator creates configuration profiles using 
profile types. 
Profile types are listed alphabetically in the middle pane of the 
Monitoring
 tab in USM.
The two kinds of profile types are:
  • Setup
     - 
    Use the setup profile types to configure how the probe operates. The setup profile types are in the lower half of the list.
  • Monitoring - Use the monitoring profile types to configure what a probe monitors, and the types of alarms and QoS metrics the probe generates. The monitoring profile types appear at the top of the profile type list. 
Some probes have a single profile type whereas others have a 
setup
 and one or more 
monitoring
 profile types. When there are several profile types, create a Setup configuration profile first. Some of the setup profile types have settings that are related to the monitoring profile types. For example, the Setup cdm profile type lets you configure sample collection intervals that apply to CPU, disk, memory, and NIC monitoring.
Mouse over fields in an MCS profile type to see tooltips that identify dependencies on other profile types.
MCS Functions
MCS performs three functions:
  • Deploys probes as needed
  • Deploys configuration profiles
  • Periodically updates probe configuration with modified configuration profiles
How Probes Are Deployed
MCS automatically deploys probes to target devices for you. When you create a configuration profile, MCS can detect if the related probe is installed on a target device. As part of the configuration deployment process, MCS deploys the probe, if necessary, and then deploys the configuration profile to a target device.
Create Configuration Profiles
A monitoring administrator creates configuration profiles using the profile types displayed on the 
Monitoring
 tab. MCS locks a profile while it is being deployed to a target device. When you mouse over a profile name, a lock icon appears. When deployment is complete, MCS unlocks the configuration profile and the lock icon disappears. Deployment details appear at the bottom of the configuration profile page. 
Create configuration profiles that match the computer resources on a target device. For example, if the target device has a MySQL database, you wouldn't create an Oracle configuration profile. If you create a configuration profile that does not apply to a target device, MCS deploys the probe and configuration profile. However, no monitoring is performed.
Copy Configuration Profiles
It is best to create configuration profiles for a device, then test the configuration profile in a test environment. After you test a profile, you can copy a configuration profile to other USM groups or devices in your environment. The copy option appears on a configuration page after MCS deploys the profile to a target device. Copying configuration profiles saves time and provides consistent monitoring among devices.
(CA UIM 8.4 to CA UIM 8.5) Select a device type for a USM group before you copy a configuration profile to a group.
See the Monitoring Configuration Service topic on the 
CA Unified Infrastructure Management
 for more information.
Filtering Extensive Drop-Down Lists
Some of the configuration fields have a large number of available options. For these fields, a filtering mechanism automatically appears above the field. 
 
To use the filter:
 
  1. Enter the first few letters of a desired option in the 
    Filter
     field. For example, enter 'Win' for Windows options.
     The search filter is case-sensitive.
  2. Select the 
    Activate Filter
     checkbox.
  3. Open the drop-down list for the configurable field. The drop-down list is now filtered based on the characters you entered in the 
    Filter
     field.
MCS Profile Types
Each of the MCS Profile types enables you to create a configuration profile that is customized for monitoring a specific type of resource. 
For information about minimum probe version required for migrating legacy profiles and the latest MCS template version supporting enhanced profiles, see Configuring Alarm Thresholds in MCS.
Use the following links to view a few examples of how to use profile types to create configuration profiles.
Active Directory Events Include and Exclude
Active Directory Response
Active Directory Server
Amazon Web Services (AWS)
Apache
Application Discovery Scripts
Azure
CA App Experience Analytics Log Analytics
See Integrate CA App Experience Analytics article to review the components that must be installed before you can use any of the Log Analytics profile types on the 
Monitoring
 tab. The related profile types available are:
CPU, Disk, Memory, and NIC Monitoring
File and Directory Scan Monitoring
Docker
DNS Response
Email Response
Exchange Monitor
Event Log Files
IIS
LDAP Response
MS Exchange Server Response
MySQL
Network Connection
NT Performance Metrics
Nutanix
Openstack
Oracle
Office365
PostgreSQL
Processes
Remote System Probe (RSP)
SAP Basis
SharePoint
SNMP Protocol Gateway
SQL Server
Telemetry
URL Check
Windows Services
VMware