aws MCS Profile Type Configuration

A monitoring administrator uses Monitoring Configuration Service (MCS) to create configuration profiles for groups of devices.
uimpga-ga
aws_mcs
A monitoring administrator uses Monitoring Configuration Service (MCS) to create configuration profiles for groups of devices.
 
Warning!
 You cannot configure a probe through the probe configuration GUI after you apply the MCS profile type to an instance of the probe. We recommend that you test your configuration before applying the configuration to many systems. To delete the configuration that is applied by MCS, you must delete the profile in MCS and then manually delete the probe. When you delete a profile, a lock icon might appear during the deletion process. Do not delete the probe until the profile is completely removed. Once the MCS configuration is deleted, you can manually redeploy the probe and configure monitoring through the probe configuration GUI.
Prerequisites
Verify the following information before you create a monitoring configuration profile:
  • Verify that your CA UIM version is at least version 8.5.1 - required by the MCS profile types.
  • Verify that your archive contains an aws probe that is at least version 5.21.
  • Complete any probe-specific prerequisites.
  • Verify that you meet the minimum hardware and software requirements before you deploy a monitoring configuration profile.
  • Verify that you have a valid license for the probe.
To use the enhanced profiles, you need the following software environment:
  • CA Unified Infrastructure Management version 9.0.2
  • Monitoring Configuration Service (MCS) version 9.02 (or later)
  • Metrics plug-in version 7.96 (or later)
  • Robot version 7.96 (or later)
Enhanced Profiles in MCS
CA UIM 9.0.2 includes a new type of Monitoring Configuration Service (MCS) profile, called an enhanced profile. Enhanced profiles provide a consistent way to configure alarms using MCS. Enhanced profiles enable you to configure metrics, baselines, alarm thresholds, Time Over Threshold alarms, and create custom alarm messages, all within a single MCS profile. For more information, see Configuring Alarm Thresholds in MCS in CA UIM Probe Documentation.
You can convert your existing MCS profiles to enhanced profiles. We recommend that you first migrate existing profiles to the latest available version and then convert them to enhanced profiles. For more information, see Migrating and Converting Existing Profiles.
AWS Profile Types and Default Settings
Use the AWS profile types to create configuration profiles for AWS subscriptions. Some of the profile types contain default monitor and alarm settings. These default settings are provided so you can configure your probes to collect data for the predefined probe dashboards in UMP. The predefined dashboards display the data that we recommend for monitoring various devices and services in your environment. Deploy all the monitoring profiles with default settings to automatically enable the metrics required by the predefined probe dashboards.
 If you deactivate any of the default metric settings, your predefined probe dashboards might not populate correctly. The default metrics required by a dashboard are included in the article for the specific dashboard.
The following table lists the AWS profile types.
Profile Type
Notes
AWS General Probe Configuration
This profile is required to configure general settings for the probe.
AWS Resource
This profile is required to connect to an AWS environment.
AWS Auto Scaling
This profile contains default metric and alarm settings.
AWS DynamoDb
This profile contains default metric and alarm settings.
AWS EC2
This profile contains default metric and alarm settings.
AWS ECS
This profile contains default metric and alarm settings.
AWS ElastiCache
This profile contains default metric and alarm settings.
AWS ELB
This profile contains default metric and alarm settings.
AWS RDS
This profile contains default metric and alarm settings.
AWS ROUTE53
This profile contains default metric and alarm settings.
AWS S3
This profile contains default metric and alarm settings.
AWS SNS
This profile contains default metric and alarm settings.
AWS SQS
This profile contains default metric and alarm settings.
(Version 5.25) AWS Lambda
This profile contains default metric and alarm settings.
AWS Custom Configurations
-
Create aws Configuration Profiles
Use the aws profile types to create configuration profiles. You can configure all instances of the aws probe with configuration profiles. The types quality of service metrics (QoS) that the probe can publish appear in each profile.
 We recommend that you do not activate any profiles until you complete your monitoring configuration. The probe restarts every time you activate a profile.
 
Follow these steps:
 
  1. In Unified Service Manager, expand a USM group and select a device or click a USM group.
    The USM group can be one of the predefined USM groups (for example, the Unix and Windows groups) in a test environment or a test group you created that has one device.
  2. Select the 
    Monitoring
     tab.
    The profile types that apply to the selected device or USM group appear in the middle column. If you select a device and profile types do not appear in the middle column of the Monitoring tab, deploy a robot to the device.
    The following figure shows an example of the available monitoring options when you select a device.
    Example Setup AWS profile type for a device
    The following figure shows an example of the available monitoring options when you select a USM group.
    Example Setup AWS profile type for a group  
  3. Hover over the 
    Setup aws
     profile type name, and then click '
    +
    ' to create a profile. 
     If you see a dialog with a prompt to install the probe, verify that the probe is in the archive and select 
    Yes
    .
  4. Complete and save the required settings. The resource profile type node is added under the General Probe Configuration profile. Expand the list to view the node.
  5. Hover over the 
    AWS Resource 
    node, and then click '
    +
    ' to create a resource profile. 
  6. Complete the profile setup information so that the probe can access the services in an AWS cloud environment.
    Additional profile type nodes are added under the profile. 
  7. Expand the list to view the available profile type nodes.
  8. Create and save profiles for any of the profile types as needed. For more information about the profiles, see AWS Profile Types and Default Settings
  9. (Optional) Return to any of the profiles and configure any additional metrics and alarms. Select the desired QoS metrics and alarms in the Monitor column. The available options are: 
    None:
     Choose this option if you do not want to publish data or alarms for the monitor. 
    Alarm
    : Choose this option if you only want to publish alarms for the monitor.
    Alarm and QoS:
     Choose this option if you want to publish both alarms and QoS data for the monitor.
    QoS:
     Choose this option if you only want to publish QoS data for the monitor.
  10. Save any profile changes.
  11. View the 
    Profile Status
     information to verify that the configuration profile was successfully deployed to the target device (or devices in a group if you created a group configuration profile). Profile status information appears at the bottom of the profile configuration page.