Active Discovery for AWS CloudWatch Metrics

Amazon Web Services (AWS) CloudWatch allows you to add custom metrics. You can automatically track these metrics in LogicMonitor Cloud by enabling Active Discovery in a DataSource.

Active Discovery regularly checks for changes in your monitored environment and updates the relevant resource properties. For more information, see “What is Active Discovery?

Get metrics from AWS CloudWatch

To retrieve the AWS CloudWatch custom metrics, the LM Cloud DataSource needs to call AWS CloudWatch ListMetrics with the following request parameters:

Parameter Description
namespace The name space to filter against.
metric name The name of the metric to filter against.
dimensions The list of dimensions to filter against. Each dimension contains a name and value.

The results returned by ListMetrics are not filterable by time and their content depends on the metrics available based on AWS CloudWatch’s retention for metric data:

Frequency Retention Period
Data points with a period of less than 60 seconds
(high-resolution custom metrics)
3 hours
Data points with a period of 60 seconds (1 minute) 15 days
Data points with a period of 300 seconds (5 minutes) 63 days
Data points with a period of 3600 seconds (1 hour) 455 days (15 months)

Enable Active Discovery for AWS CloudWatch

Create a new DataSource (or edit an existing AWS CloudWatch DataSource) to actively monitor AWS CloudWatch for changes:

Active Discovery is only available for multi-instance DataSources.

1. In the DataSource settings, check “Multi-instance?

2. Check “Enable Active Discovery“.

3. Under Discovery schedule, select “Only when host/DataSource added or changed”.

4. Under Discovery method, select “AWS CloudWatch”.

5. Set the Parameters:

Parameter Description
Namespace (Required) The namespace to filter the metrics.
Metric Name (Optional, available since version 136) The name of the metric to filter against. Use this to monitor a single specific metric.
Device Dimension Name (Required) The Cluster or Domain Dimension Name to filter the metrics against the device. The value is read from the AWS Properties and is case sensitive. You will need to specify which LogicMonitor property matches this in Device Dimension Value. Example: DomainName.
Device Dimension Value A wildcard value from the instance’s LogicMonitor properties. Example: ##system.aws.DomainName##
Instance Dimension (Required) The name of the dimension used to discover the nodes/instances. For example, “NodeId” adds the AWS NodeId in the metric path.
Metrics Period (Optional) Specifies how often the metrics we are trying to pull are published. If blank, it shows all metric periods.

An example of a metric path:

AWS/ES>DomainName:##system.aws.DomainName##>NodeId:##WILDVALUE##>CPUUtilization>Maximum

When instances are found, the path translates to:

AWS/ES>DomainName:testdomain>NodeId:TeSt1234>CPUUtilization>Maximum

In this Article: