aws AC Configuration

You can also include or exclude specific AWS regions and services from discovery and monitoring to optimize API usage. You can create a profile to select specific AWS region and services for discovery and monitoring. For more information, see Create a Profile.
uimpga-ga
aws_AC
This article describes the configuration concepts and procedures to set up the Amazon Web Services Monitoring (aws) probe. You can create monitoring profiles to access aws resources and retrieve data from Amazon CloudWatch. You can also configure health monitors to generate QoS and alarm messages based on the availability of services in various geographical regions. The probe retrieves data of instances or services, and allows you to generate QoS and alarm messages. You can also retrieve the list of custom metrics that are created for a specific service from the Amazon CloudWatch.
You can also include or exclude specific AWS regions and services from discovery and monitoring to optimize API usage. You can create a profile to select specific AWS region and services for discovery and monitoring. For more information, see Create a Profile.
You can configure the probe to process and send Cloudtrail logs to AXA Kafka. You can enable the probe to fetch, parse, and send the desired logs to AXA by selecting the
Cloud Trail Logs
check box and providing more details. For more information, see Create a Profile.
This article is for probe versions 4.1 or later.
The following diagram outlines the process to configure the probe.
Configuring aws probe
Configuring aws probe
Contents
2
Verify Prerequisites
Verify that required hardware and software is available and installation prerequisites and upgrade considerations are met before you configure the probe. For more information, see aws (Amazon Web Services Monitoring) Release Notes.
Amazon charges the AWS account which the probe uses to monitor the AWS services. Consider this fact while configuring the probe to monitor various AWS services.
Configure General Properties
You can configure the logging, auto discovery, and proxy properties of the probe.
Follow these steps:
  1. Select the
    aws
    node.
    The
    Probe Information
    section provides information about the probe name, probe version, start time of the probe, and the probe vendor.
  2. Under the
    Probe Setup
    section, select the level of information that is written to the log file in the Log level field. You can select the following log levels:
    • 0 - Logs only severe information
    • 1 - Logs errors information
    • 2 - Logs warnings information
    • 3 - Logs general information (default)
    • 4 - Logs debugging messages
    • 5 - Logs tracing/low-level debugging information
    Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
  3. Under the
    Auto Discovery
    section, select the time interval after which instances are auto-discovered, in the
    Discovery Interval (minutes)
    field. If any instance is added or deleted in the aws resource, then the
    Auto Discovery
    functionality automatically updates the list of instances in the probe.
    Reduce this interval to discover instances frequently. Frequent discovery can also increase aws billing costs.
  4. Under the
    Proxy Settings
    section, complete the following field information to connect to the aws cloud through a proxy server.
    • Enable Proxy:
      allows you to use a proxy server for connecting to the aws cloud.
    • IP:
      specifies the IP address or the DNS resolvable hostname of the proxy server.
    • Port:
      specifies the port on the proxy server through which the connection to AWS CloudWatch is established.
    • Username:
      defines the user name for accessing the proxy server. For more information, see the Installation Prerequisites section in aws (Amazon Web Services Monitoring) Release Notes.
      The aws probe is certified for use in Squid proxy environment.
    • Password:
      defines the password for the specified
      Username
      .
  5. (aws 5.00 and later)
    In the
    EC2 Label Property
    section >
    EC2 Label Type
    field, select from the following options to use the applicable identification for EC2 instances:
    This section is only available during initial configuration of the probe. The probe disables the field if you configure a profile.
    • Instance Id:
      enables the probe to use the Instance Id of the EC2 instances.
    • IP:
      enables the probe to use the private IP address of the EC2 instances.
    • Tag Name:
      enables the probe to use the tag names of the EC2 instances. For more information about tags, see the
      Configure EC2 Tags
      section.
  6. Click
    Save
    .
(aws 4.10 and later) Configure EC2 Tags
You can configure EC2 tags in the probe and configure templates to monitor EC2 instances with a specific tag and value. EC2 tags in AWS allow you to logically group multiple instances. The probe allows you to monitor the instances based on these groups.
Follow these steps:
  1. Select the
    aws
    node.
  2. Under the
    AWS EC2 Tags
    section, select
    New
    to add a tag to the probe.
  3. Specify a tag for the EC2 instance.
    Specify the exact tags in the probe as defined in the AWS resource.
  4. Click
    Save
    .
  5. Open the
    Template Editor
    for the probe.
  6. Configure EC2 tags in template filters, as required.
Create a Profile
You can create a profile to monitor the aws resource, where each profile represents one aws resource.
Follow these steps:
  1. Click the
    Options (icon)
    next to the
    aws
    node and select
    Add New Profile
    .
    The
    Add New Profile
    dialog appears.
  2. Specify the values in the following fields:
    • Profile Name:
      defines a unique name for the profile. You can specify the aws account name as the value for this field.
      This field was identified as
      Name
      in version 3.5 of the probe.
    • Active:
      allows you to activate the profile for monitoring, on creation.
    • Interval (secs):
      specifies the time interval (in seconds) after which the profile again collects the data from the aws cloud. CA recommends you to specify a value of 300 seconds or greater.
      Default: 600
      Reduce this interval to generate alarms and QoS frequently. A shorter interval can also increase the system load and terminate the data collection before completion.
    • Alarm Message:
      specifies the alarm to be generated when the connection to aws services fails.
      Default: ResourceCritical
    • IAM Role Based Authentication:
      It allows you to connect to the AWS resource without Access key and Secret key when the probe is deployed on an EC2 instance. By default, this option is not enabled, and you must use the combination of Access Key and Secret Key to access the AWS resource.
    • Access Key Id:
      defines the login credential of the aws user account.
    • Secret Key:
      specifies the additional log in credential of the aws user account.
      • The probe uses the combination of the
        Access Key Id
        and
        Secret Key
        to access the aws resource.
      • If the
        IAM Role Based Authentication
        option is enabled, the
        Access Key
        and
        Secret Key
        fields are disabled. The probe must be deployed on an EC2 instance.
    • Cloud Trail Logs:
      Check this box to send CloudTrail Logs to AgileOps Analytics Platform.
    • CloudTrail SQS Queue URL:
      Enter the URL of SQS Queue that will receive notifications for CloudTrail Logs.
    • AgileOps Analytics Tenant ID:
      Enter the AgileOps Analytics Platform Tenant ID.
    • AgileOPs Analytics Kafka Broker List:
      Enter the AgileOps Analytics Platform Kafka Host and port details in the form of kafka_host1:kafka_port1;kafka_host2:kafka_port2.
    • AgileOPs Analytics Elasticsearch URL:
      Enter AgileOps Analytics Platform Elasticsearch REST API URL; For a multi-node cluster deployment provide the Elasticsearch Client Node hostname.
  3. Click
    Submit.
    The monitoring profile appears under the aws node in the navigation pane. The Auto Discovery functionality automatically loads a list of all the available instances. The aws services nodes are visible in the navigation pane only after you create a monitoring profile. Initially, only the aws node and the aws Service Health node are visible.
  4. Click the profile name to view the
    AWS
    Region Configuration
    above the profile details on the right pane.
  5. Click the appropriate region from the
    region
    list to view various AWS services for the selected region.
  6. Check the appropriate check box for including the services for discovery and monitoring.
  7. Refresh the GUI after the probe restarts.
    When you save the configuration, the probe restarts and collects data for AWS services again. This re-discovery of services slows the GUI processing. Ensure that rediscovery is complete before further configuration.
  8. Select the
    profile name
    node and click
    Actions > Verify Credentials
    to verify the credentials of the profile.
  9. Select the
    profile name
    node and click
    Actions > Verify TenantID
    to verify the AgileOps Analytics Tenant ID with respect to the AgileOPs Analytics Elasticsearch URL.
  10. (Optional - aws 5.00 to 5.11)
    Specify the values in the following fields to calculate the estimated billing charges of the AWS root and linked accounts, if applicable:
    From version 5.20, the probe uses the credentials specified in
    Step 2
    to retrieve monitoring information for the
    AWS Billing and Cost Management
    service.
    • Payer Account Access Key Id:
      defines the login credential of the aws payer user account.
    • Payer Account Secret Key:
      specifies the additional login credential of the aws payer user account.
      The probe uses the combination of the
      Payer Account Access Key Id
      and
      Payer Account Secret Key
      to access the aws resource.
    • Linked Account Number:
      specifies the account number of the linked aws account. Leave this field blank to monitor the billing details of the primary AWS account.
  11. (Optional - aws 5.00 to 5.11)
    Click
    Actions > Verify Payer Credentials
    to verify the credentials of the linked account.
  12. Click
    Save
    .
You can also go through the video for a brief demonstration on how to create profiles and perform basic troubleshooting on the probe.

AWS Components for Monitoring
Each profile is associated with an inventory of various AWS services. Expand and click nodes in a profile to view the services and any associated monitors. Each profile node contains the following nodes:
  • Hostname: An organizational node with the response time monitor of the aws account.
  • Detached Configuration: An organizational node that contains information about resources with active monitors where data could not be collected. This state frequently occurs when a monitored resource is deleted. For example, a monitored EC2 instance is deleted from the server before its monitoring is deactivated. The probe keeps sending false alarms for the EC2 instance because the probe is unable to retrieve the details. The EC2 instance is also not visible on the probe GUI navigation pane.
  • Service name: An organizational node that represents the AWS services available for monitoring.
The following figure shows the probe configuration GUI navigation pane inventory. You might see some differences in your GUI depending on your environment, probe, and Admin Console versions.
awsProbeGUI.png
Monitor AWS Services
You can define monitors for aws services, as required, and configure monitor properties to generate QoS. CA recommends that you use this procedure only if you need to collect data for a few components. If you must collect similar types of data for many components, use a template to configure monitoring and alarms. The nodes in the profile tree have monitors for applicable nodes. You can filter through the nodes to configure the monitors for the required component.
You can configure the following services:
3
(aws 5.25 and later) Monitor Service Instances
You can configure the probe and monitor the instance count of multiple AWS services. You can generate QoS and alarms for the following instances of AWS services:
  • Total Active EC2 Instances
  • Total EBS Instances
  • Total VPC Instances
  • Total RDS Instances
  • Total Auto Scale Instances
  • Total DynamoDB Instances
  • Total ECS Instances
  • Total Route53 Instances
  • Total ElastiCache Instances
  • Total SNS Instances
  • Total SQS Instances
  • Total ELB Instances
  • Total S3 Instances
The probe uses the interval specified during profile creation for these monitors.
Follow these steps:
  1. Navigate
    aws >
    profile name
    >
    Host name
    node and select the monitor to configure.
  2. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  3. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  4. Click
    Save
    .
(aws 5.00 and later) Monitor Billing Details of AWS Services
You can monitor the estimated billing charges, in US Dollars, for the following services:
  • DynamoDB
  • Elastic Compute Cloud (EC2)
  • ElastiCache
  • Lambda
  • Relational Database Service (RDS)
  • Route 53
  • Simple Notification Service (SNS)
  • Simple Queue Service (SQS)
  • Simple Storage Service (S3)
Follow these steps:
  1. Navigate to the required
    Service name
    node and select the
    EstimatedCharges
    monitor in the
    Monitors
    section.
    The Statistics and Period field values do not impact the billing information monitored by the probe.
  2. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  3. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  4. Click
    Save
    .
    Verify the billing access to the AWS credentials if the probe incorrectly generates a zero value for the monitor.
Monitor AutoScaling Service
You can configure the probe to monitor autoscaling groups and instances. Auto-scaling groups are configured in the aws Management Console. You can configure the AutoScaling QoS metrics through the available regions, for example, Asia Pacific (Singapore) Region.
You can configure the
Autoscaling Group
to view the groups, devices, and metrics in USM. You can create auto-scaling groups in USM by using the advanced filter attribute AWSAutoScalingGroup. For more information, see the
Create and Manage Groups in USM
section in the CA UIM documentation.
The probe generates alarm and QoS data of the AutoScaling instances according to the values retrieved from the aws CloudWatch.
Follow these steps:
  1. Navigate to
    aws >
    profile name
    >
    AutoScaling
    node.
  2. Under the
    AutoScaling Configurations
    section, update the following field information:
    • Active:
      allows you to activate the instances of the aws resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the
      Unified Management Portal (UMP)
      are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
(aws 5.00 and later) Monitor DynamoDB Service
You can configure the probe to connect to the Amazon DynamoDB database service and collect information about the performance of the database tables and indexes. The probe generates alarm and QoS data for the DynamoDB service of each region according to the values retrieved from the aws CloudWatch.
The probe uses the
Sum
statistics on the collected values for the following DynamoDB metrics.
  • Read Throttle Events
  • Write Throttle Events
  • System Errors
  • Put Item Throttled Requests
  • Delete Item Throttled Requests
  • Update Item Throttled Requests
  • Get Item Throttled Requests
  • Batch Get Item Throttled Requests
  • Batch Write Item Throttled Requests
  • Scan Throttled Requests
  • Query Throttled Requests
  • Get Records Throttled Requests
You cannot change the value of the statistics. The probe uses the
Average
statistics on the collected values for the remaining DynamoDB metrics.
Follow these steps:
  1. Navigate to
    aws >
    profile name
    > DynamoDb
    node.
  2. Under the
    DynamoDb Configurations
    section, update the following field information:
    • Active:
      allows you to activate the profile.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved at 5 minute intervals.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
(aws 5.00 and later) Monitor ECS Service
You can configure the probe to retrieve Amazon EC2 Container Service information. The probe retrieves the values of the ECS clusters and services of a specific region from the aws CloudWatch. You can configure the following monitors to generate QoS and alarm messages:
  • ECS Clusters: CPU and Memory reservation and utilization
  • ECS Services: CPU and Memory utilization
The AWS ECS service is a scalable and fast container management service. You can also configure monitors for the EC2 instances in each cluster. For more information, see
Monitor EC2 Service
.
Follow these steps:
  1. Navigate to
    aws >
    profile name
    >
    ECS
    node.
  2. Under the
    EC2 Configurations
    section, update the following field information:
    • Active:
      allows you to activate the instances of the aws resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Monitor EC2 Service
You can configure the probe to connect to the EC2 service and collect data about the instances of the aws resource. The probe generates alarm and QoS data of the EC2 service of a specific region according to the values retrieved from the aws CloudWatch. The performance counters are divided into following categories:
  • Operational and power state of the instance
  • CPU
  • Disk
  • Network
  • Volumes
  • Elastic Block Storage (EBS)
    The
    EBS
    node is visible in the navigation panel only if you have added a storage block with the EC2 instances, or when you have assigned a storage block to the instances.
The AWS EC2 service of a specific region stores the instance data in aws CloudWatch. An EC2 instance is a virtual machine (VM). If any region subscribes to the EC2 service, then an instance of EC2 VM is created for that region. The probe monitors the performance counters of the EC2 instances of the AWS resource. All EC2 instances are visible under the EC2 node.
Follow these steps:
  1. Navigate to
    aws >
    profile name
      >
    EC2
    node.
  2. Under the
    EC2 Configurations
    section, update the following field information:
    • Active:
      allows you to activate the instances of the aws resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Monitor ELB Service
You can configure the metrics of those EC2 instances that are registered with ELB layer that you are currently monitoring. The probe monitors the ELB layer that distributes the incoming application data between multiple EC2 instances. The probe generates QoS data based on the inputs recived from the EC2 instances at group level. You can configure the ELB QoS metrics through the available regions, for example, Asia Pacific (Singapore) Region.
By default, the probe uses the following statistics on the collected values for each ELB metric. You cannot change the value of the statistics.
  • Sum
    • Request Count
    • HTTPCode_ELB_4XX
    • HTTPCode_ELB_5XX
    • HTTPCode_Backend_2XX
    • HTTPCode_Backend_3XX
    • HTTPCode_Backend_4XX
    • HTTPCode_Backend_5XX
    • Backend Connection Errors
    • Spillover Count
  • Average
    • Healthy Host Count
    • Unhealthy Host Count
    • Latency
  • Maximum
    • Surge Queue Length
Follow these steps:
  1. Navigate to
    aws >
    profile name
    >
    ELB
    node.
  2. Under the
    Elastic Load Balancing
    section,
    update the following field information:
    • Active:
      allows you to activate the monitoring of the ELB layer.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Monitor ElastiCache Service
You can configure the probe to retrieve ElastiCache instance information. The probe generates alarm and QoS data of the Elasticache service of a specific region according to the values retrieved from the aws CloudWatch. You can configure monitors for the Elasticache instance and its CPU and memory.
The AWS ElastiCache service provides a scalable cache to store temporary data and supports the following types of cache engines. Corresponding aws instances are displayed in the navigation pane according to the type of cache engine.
  • Remote Dictionary Server or Redis (Currently, ElastiCache supports a single-node Redis cache cluster)
  • Memcached (Currently, ElastiCache supports a maximum of 20 nodes in a cache cluster)
Follow these steps:
  1. Navigate to
    aws >
    profile name
    >
    node.
  2. Under the
    ElastiCache Configurations
    section, update the following field information:
    • Active:
      allows you to activate the instances of the aws resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
(aws 5.25 and later) Monitor Lambda Service
You can configure the probe and retrieve monitoring information from the CloudWatch and generate QoS and alarms for each AWS Lambda compute service.
Follow these steps:
  1. Navigate
    aws >
    profile name
    > Lambda
    node.
  2. Under the
    Lambda Configurations
    section,
    update the following field information:
    • Active:
      allows you to activate monitoring of the AWS Lambda service.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Monitor RDS Service
You can configure the RDS service to manage the relational databases that are stored on AWS CloudWatch. The probe retrieves the data from the CloudWatch and generates QoS related to an RDS instance. You can configure the monitoring parameters of each database and the following components:
  • CPU
  • Disk
  • Memory
  • Network
The
ReplicaLag
monitor is only available for databases where the Amazon RDS Read Replica feature is enabled. The
Bin Log
monitor is only available for non-SQL Server RDS instances.
Follow these steps:
  1. Navigate
    aws >
    profile name
    > RDS
    node.
  2. Under the
    RDS Configurations
    section,
    update the following field information:
    • Active:
      allows you to activate the addition of database instances of the AWS resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
(aws 5.00 and later) Monitor Route 53 Service
You can configure the probe to connect to the Amazon Route 53 service and collect information about the performance of the DNS service. The probe generates alarm and QoS data for the service according to the values retrieved from the aws CloudWatch. By default, the probe uses the
Minimum
statistics on the collected values for the
HealthCheckStatus
monitor.
Follow these steps:
  1. Navigate to
    aws >
    profile name
    > ROUTE53
    node.
  2. Under the
    Route53 Configurations
    section, update the following field information:
    • Active:
      allows you to activate the instances of the aws resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Monitor SNS Service
You can configure the SNS service to monitor the topic for which the publisher sends notifications to the subscriber. You can configure the SNS QoS metrics through the available regions, for example, Asia Pacific (Singapore) Region. The probe generates QoS data of the SNS service according to the values retrieved from AWS CloudWatch.
By default, the probe uses the following statistics on the collected values for each SNS performance counter. You cannot change the value of the statistics.
  • Sum
    • Number Of Messages Published
    • Number Of Notifications Delivered
    • Number Of Notifications Failed
  • Average
    • Publish Size
Follow these steps:
  1. Navigate to
    AWS >
    profile name
    >
    SNS
    node.
  2. Under the
    SNS Configurations
    section, update the following field information:
    • Active:
      allows you to activate the monitoring SNS topic.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
      By default, for an active topic, the AWS CloudWatch receives metrics after every 5 minutes. Default monitoring, and monitoring per minute is not available for aws SNS.
  3. Navigate to the required node and select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Monitor SQS Service
You can configure the SQS service to send data from an AWS service to any other AWS service. The probe monitors the properties of a queue based on the data collected from the aws CloudWatch in a specific region. You can configure the SQS QoS metrics through the available regions, for example, Asia Pacific (Singapore) Region. The probe generates QoS data of the SQS service according to the values retrieved from AWS CloudWatch. By default, the probe uses the following statistics on the collected values for each SQS metric:
  • Number of Messages Sent: Sum
  • Sent Message Size: Average
  • Number of Messages Received: Sum
  • Number of Empty Receives: Sum
  • Number of Messages Deleted: Sum
  • Approximate Number of Messages Delayed: Average
  • Approximate Number of Messages Visible: Average
  • Approximate Number of Messages Not Visible: Average
    You cannot change the value of the statistics.
Follow these steps:
  1. Navigate to
    aws >
    profile name
    >
    SQS
    node.
  2. Under the
    SQS Configurations
    section, update the following field information:
    • Active:
      allows you to activate the monitoring of the SQS queue.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  4. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  5. Click
    Save
    .
Monitor S3 Service
You can configure the performance counters for AWS Simple Storage Service (S3). The data which is stored in the cloud using the AWS S3 service is segregated into groups that are known as buckets. The probe monitors the time which is consumed in storing and retrieving files to and from the bucket, respectively. The probe generates QoS data related to the time that is consumed in storing and retrieving files to and from the S3 buckets.
Set the polling interval (
Interval
field in the
Add New Profile
section in
aws
node) according to the size of the file that you want to store or retrieve. If the polling interval is too less, then the probe starts retrieving data again from the bucket before completing a previous file process. For example, if you want to upload a file of size 1 MB then you can set the polling interval as 5 minutes.
Follow these steps:
  1. Navigate to
    aws >
    profile name
    >
    S3
    node.
  2. Under the
    S3 Configurations
    section, update the following field information about the file bucket so that the probe can monitor the time that is consumed in accessing the file bucket:
    • Active
      : enables the monitoring of file bucket access time.
    • (aws 4.10 and earlier) Bucket Name
      : specifies the name of the file bucket for which the probe monitors the storing and retrieving time.
    • File Name
      : defines the name of the file which is stored or retrieved from the bucket. You can browse and select the file. The probe includes a file with the name
      s3TestDocument.txt
      .
  3. Select the monitor to configure.
  4. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  5. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  6. Click
    Save
    .
Configure Custom Metric
In aws, metrics are segregated into different
Namespaces
. A
Dimension
is a variable that categorizes a metric according to its statistics. When you create custom metrics through the script and store the metrics in AWS CloudWatch, the probe retrieves that data from CloudWatch. You can select a custom metric that is available in an aws Namespace and then define custom QoS for it. You can configure any of the discovered metrics that are available in an aws Namespace through the
Custom Metrics
node except RDS, EC2, EBS, ElastiCache, SQS, SNS, ELB, and AutoScaling.
Follow these steps:
  1. Navigate to
    aws >
    profile name >
    Custom Metric
    node.
  2. Under the
    Custom Configurations
    section, update the following field information:
    • Active:
      allows you to activate the custom instances of the aws resource.
    • Statistics:
      defines one of the following operations to be performed on the sample values that the probe retrieves:
      • Calculate minimum value
      • Calculate maximum value
      • Calculate the sum of all the values
      • Calculate the average of all the values (Default)
      When you change the Statistics value, the QoS graphs on the UMP portal are changed.
    • Time Duration:
      specifies the time duration (in minutes) to collect sample values from AWS CloudWatch. The probe collects the values that are calculated during the specified time period.
    • Period (minutes):
      specifies a time interval, in minutes, that is used to divide the collected values into groups. For example, if the
      Time Duration
      is specified as 10 minutes and the
      Period
      is specified as 2 minutes, then the values are retrieved for 5 minutes time interval.
  3. Select the required metrics from the list of available AWS Namespaces that the probe retrieves from CloudWatch in
    Available Service Metrics
    field. Each Namespace contains various custom metrics. You can move specific service Namespace from the
    Available List
    to the
    Selected List
    . The selected service metrics are visible as nodes in the navigation pane.
    You must include
    Namespace
    and
    Dimensions
    in a custom metric script for the probe to collect the metrics.
  4. Navigate to
    Custom Metric >
    Namespace name
    node.
    If you have created the custom metrics in a custom Namespace then only custom metrics are visible in the table. However, if you have created the custom metrics in an existing Namespace then all the metrics are visible in the table.
  5. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  6. Update the following field information to configure the QoS properties of the custom metric:
    • QoS Name:
      specifies a name for the custom QoS.
      CA recommends you to specify a unique name for the QoS.
    • QoS Unit:
      specifies a unit for the custom QoS.
  7. Select
    Compute Baseline
    to enable thresholds. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  8. Click
    Save
    .
Monitor Geographical Service Health
You can monitor the AWS service availability for a specific region. The probe generates QoS and alarm messages when a service in the specified region is unavailable. The probe generates the following alarm and QoS messages for the health of the AWS services:
  • Disruption in the service
  • Performance issues
  • Service is operating normally
  • Other information
Follow these steps:
  1. Navigate to
    aws >
    AWS Service Health
    node.
  2. Under the
    Health Configuration
    section, specify the
    Health Interval (mins)
    value. You can specify the time interval, in minutes, after which the probe retrieves the health status of the aws services.
    Default: 60
    Reduce this interval to generate alarms frequently. A shorter interval can also increase the system load.
  3. Specify the
    Time Range (hours)
    value. The probe does not generate alarms for service health data generated earlier than this time range.
    Default: 48
  4. Navigate to the
    aws > AWS Service Health >
    node.
    The list of aws services that are available for a specific region are displayed under
    AWS Service Status
    section.
  5. Select the
    Publish Data
    and
    Publish Alarms
    fields to retrieve QoS data and generate alarm messages, respectively.
  6. The value of the
    Alarm
    column in the table changes from
    Off
    to
    On
    .
Create Templates to Configure Multiple Profiles
You can create templates in the probe to configure multiple existing profiles with the same monitor configuration. For more information, see aws Apply Monitoring with Templates.
The probe applies all template configuration, including filters, rules, and monitors in the next monitoring interval. However, when you remove an applied template, the probe can take 3 to 4 intervals before the template configuration is reverted.
The probe includes default templates with the monitors that are configured for the default USM views.
  • On Unified Dashboard 3.04 and earlier, and on upgrade to Unified Dashboard 3.05, the
    Template Editor
    interface of the probe includes a
    Factory_Template
    with recommended configuration for multiple AWS services.
  • From Unified Dashboard 3.05, probe also includes default templates with recommended configurations for individual AWS services. For example, Auto Scaling Factory Template.
From probe version 4.10, you must create a copy of a default template to use it. For more information, see the
Upgrade Considerations
section in aws (Amazon Web Services Monitoring) Release Notes.
View Probe Data
There are several locations where you can view aws probe data.
Verify that you are viewing the correct information for your CA UIM version.
AWS Unified Dashboards
The Unified Management Portal (UMP) includes predefined dashboards to view the probe data. The default templates in the Template Editor interface include the monitors that are configured for the respective Unified Dashboards. For detailed descriptions and required data sources, see the following articles:
unified_dashboard 3.04 and earlier
On upgrade to Unified Dashboards 3.05 or later, the probe continues to display this dashboard on UMP. However, CA recommends you to use the individual dashboards available for the probe.
unified_dashboard 3.05 and later
CABI for CA UIM Dashboards
The Unified Management Portal (UMP) includes a predefined Amazon Web Services (AWS) CABI dashboard to view the probe data. The default templates in the Template Editor interface include the monitors that are configured for the dashboard. For detailed descriptions and required data sources, see AWS CABI for CA UIM Dashboards.
(Optional) Create AWS Groups in USM
You can configure Amazon Web Services groups in Unified Service Manager (USM) to view AWS metric data.
Follow these steps:
  1. Verify that the probe configuration is complete.
  2. Go to USM and create a group.
  3. Add at least one advanced filter to the group
  4. (Optional - AWS Auto Scaling Groups)
    Use the Advanced filter attribute
    AWSAutoScalingGroup
    and the
    ASG
    names for the values.
  5. (Optional - AWS EC2 Filters)
    Specify advanced filters in the
    UserProp.<name>
    format.
    For more information, see the following sections in Create and Manage Groups in USM.
    • Create a Group to Display Auto-Scaling Metrics for AWS
    • Filters for Amazon EC2 Instance Groups
    From aws version 5.25, you can use the AWSComputerNameInTags advanced filter to include EC2 instances using their name tags. You can also use the ComputerName advanced filter to use the EC2 instance IDs.
  6. (Optional - AWS VPC)
    Use the Advanced filter attributes
    AWSAutoScalingGroup, AWSVPCId,
    or
    AWSSubnetId
    to implement VPC filters.
  7. (aws 5.25 and later - Optional - AWS Accounts)
    Use the advanced filter attribute
    AWSUserName
    to filter using AWS accounts.
You can also go through the video for a brief demonstration.

aws FAQs
Why do I see “Throwing InterruptedException to allow shutdown” messages in my probe log after I change the configuration on a running probe?
  • This message is generated when a probe is attempting to process data, and a configuration change causes the probe to restart. For example, the probe might be waiting for a response from a service’s API.  This message is most frequently seen when a MCS configuration profile is applied to a running probe, but this message might be generated for any configuration change that restarts the probe. This is not a serious problem and only occurs during the probe configuration process.
How do I delete a profile in the aws probe configuration GUI?
  • Click a profile node in the aws probe configuration GUI. Select
    Options (icon) > Delete Profile
    .
How do I modify a profile in the aws probe configuration GUI?
  • Click a profile node in the aws probe configuration GUI. Go to the details pane, make your changes, and then click
    Save
    .
Why did my configuration settings disappear after I refreshed or reopened the aws probe configuration GUI?
  • Verify that you clicked
    Save
    to load your configuration changes in the aws probe configuration GUI.
Why is my profile in a pending state?
  • The aws probe inventory can take some time to appear in the GUI or your profile might contain incorrect information and be unable to connect to the cloud deployment. You can verify if the probe has successfully made a connection to the cloud. Click a profile node in the aws probe configuration GUI. Go to the details pane and click
    Actions > Verify Selection
    .
Can I deactivate an active probe template?
  • Yes. Go to the aws probe configuration GUI and click
    Template Editor
    . Click the appropriate template name, go to the details pane, and remove the check in the
    Active
    checkbox.
How do I delete a probe template or filter?
  • Verify that the template is inactive, and perform one of the following steps:
    • To delete a template, click the appropriate template name in the Template Editor and then click
      Options (icon) > Delete Template
      .
    • To delete a filter, click the appropriate filter name in the Template Editor and then click
      Options (icon) > Delete Filter
      .
Why can't I change a monitor setting in the aws probe configuration GUI?
  • Verify that there is not a "This configuration is managed by Templates", message. You cannot modify a configured monitor in the openstack probe configuration GUI once you activate a template.
How can I tell what monitors are included in a template?
  • Go to
    Template Editor > aws probe >
    template name
    . Go to the details pane and look at the monitors Included in Template table.
Can I modify a template?
  • Yes. Go to the aws probe configuration GUI and click Template Editor. Verify that the template you want to edit is inactive. Make your changes to the appropriate template item and click Save.
How do I stop receiving alerts of a monitored component that I have deleted from the server?
  • Go to the probe configuration GUI and click
    Profile name > Detached Configuration
    . Select the appropriate component and click
    Options (icon) > Delete
    .