         | Did this page help you? Yes No Tell us about it... |
Amazon CloudWatch Metrics, Namespaces, and Dimensions Reference
Topics
- AWS Namespaces
- AWS Billing Dimensions and Metrics
- Dimensions for AWS Billing Metrics
- Amazon DynamoDB Dimensions and Metrics
- Amazon EBS Dimensions and Metrics
- Amazon EC2 Dimensions and Metrics
- Amazon Elastic MapReduce Dimensions and Metrics
- Amazon RDS Dimensions and Metrics
- Amazon SNS Dimensions and Metrics
- Amazon SQS Dimensions and Metrics
- AWS Storage Gateway Dimensions and Metrics
- Auto Scaling Dimensions and Metrics
- Elastic Load Balancing Dimensions and Metrics
AWS Namespaces
All AWS services that provide Amazon CloudWatch data use a namespace string, beginning with "AWS/". The following services push metric datapoints to CloudWatch.
| AWS Product | Namespace |
|---|---|
|
AWS Billing |
|
|
Amazon DynamoDB |
|
|
Amazon Elastic Block Store |
|
|
Amazon Elastic Compute Cloud |
|
|
Amazon Elastic MapReduce |
|
|
Amazon Relational Database |
|
|
Amazon Simple Notification Service |
|
|
Amazon Simple Queue Service |
|
|
Amazon Storage Gateway |
|
|
Auto Scaling |
|
|
Elastic Load Balancing |
|
AWS Billing Dimensions and Metrics
| Metric | Description |
|---|---|
|
The estimated charges for your AWS usage. This can either be estimated charges for one service or a roll-up of estimated charges for all services. |
Dimensions for AWS Billing Metrics
AWS Billing sends the ServiceName and LinkedAccount dimensions to Amazon CloudWatch.
| Dimension | Description |
|---|---|
|
The name of the AWS service. This dimension is omitted for the total of estimated charges across all services. |
|
The linked account number. This is used for consolidated billing only. This dimension is omitted for thte total of all accounts. |
Amazon DynamoDB Dimensions and Metrics
Amazon DynamoDB Dimensions and Metrics
The following metrics are available from the Amazon DynamoDB Service. The service only sends metrics when they have a non-zero value. For example, if no requests generating a 400 status code occur in a time period, you would see no data for the UserErrors metric that reports requests generating a 400 status code.
![[Note]](http://docs.amazonwebservices.com/docs-common/images/note.png) | Note |
|---|---|
The Statistic values available through Amazon CloudWatch, such as
|
| Metric | Description | |||
|---|---|---|---|---|
SuccessfulRequestLatency |
The number of successful requests in the specified time
period. By default,
View (namespace): Units: Milliseconds (or a count for SampleCount) Valid Statistics: Minimum, Maximum, Average, SampleCount | |||
UserErrors |
The number of requests generating a 400 status code (likely indicating a client error) response in the specified time period. View (namespace): Units: Count Valid Statistics: Sum, SampleCount | |||
SystemErrors |
The number of requests generating a 500 status code (likely indicating a server error) response in the specified time period. View (namespace): Units: Count Valid Statistics: Sum, SampleCount | |||
ThrottledRequests |
The number of user requests that exceeded the preset provisioned throughput limits in the specified time period. View (namespace): Units: Count Valid Statistics: Sum, SampleCount | |||
ConsumedReadCapacityUnits |
The amount of read capacity units consumed over the specified time period, so you can track how much of your provisioned throughput is used. For more information, see Provisioned Throughput in Amazon DynamoDB. View (namespace):
View (namespace): Units: Count Valid Statistics: Minimum, Maximum, Average, Sum | |||
ConsumedWriteCapacityUnits |
The amount of write capacity units consumed over the specified time period, so you can track how much of your provisioned throughput is used. For more information, see Provisioned Throughput in Amazon DynamoDB.
View (namespace): Units: Count Valid Statistics: Minimum, Maximum, Average, Sum | |||
ReturnedItemCount |
The the number of items returned by a Scan or Query operation. View (namespace): Units: Count Valid Statistics: Minimum, Maximum, Average, SampleCount, Sum |
Dimensions for Amazon DynamoDB Metrics
The metrics for Amazon DynamoDB are qualified by the values for the account, table name, or operation. Account level metrics display when you select AWS/DynamoDB as the viewing option. Otherwise, Amazon DynamoDB data can be retrieved along any of the following dimensions in the table below. Some metrics allow you to specify both a table name and operation, depending on the viewing option you specify.
|
Dimension |
Description |
|---|---|
TableName
|
This dimension limits the data you request to a specific table. This value can be any table name for the current account. |
Operation
|
The operation corresponds to the Amazon DynamoDB service API, and can be one of the following:
For all of the operations in the current Amazon DynamoDB service API, see Operations in Amazon DynamoDB. |
Amazon EBS Dimensions and Metrics
Amazon Elastic Block Store sends data points to Amazon CloudWatch for several metrics. All mounted Amazon EBS volumes automatically send five-minute metrics to Amazon CloudWatch. Detailed monitoring, or one-minute metrics, is currently unavailable for Amazon EBS volumes.
Amazon EBS Metrics
You can use the Amazon CloudWatch GetMetricStatistics API to get any of the
Amazon EBS volume metrics listed in the following table. The period for all the metrics is 5 minutes,
which means the system reports one data point every 5 minutes for each metric for each volume, and that
data point covers the volume's previous 5 minutes of activity.
The following table groups metrics that are similar. The metrics in the first two rows are also available for the local stores on Amazon EC2 instances.
| Metric | Description |
|---|---|
|
|
The total number of bytes transferred in the period. Units: Bytes |
|
|
The total number of operations in the period. Units: Count |
|
|
The total number of seconds spent by all operations that completed in the period. If multiple requests are submitted at the same time, this total could be greater than the length of the period. For example, say the period is 5 minutes (300 seconds); if 700 operations completed during that period, and each operation took 1 second, the value would be 700 seconds. Units: Seconds |
|
|
The total number of seconds in the period when no read or write operations were submitted. Units: Seconds |
|
|
The number of read and write operation requests waiting to be completed in the period. Units: Count |
Amazon EC2 Dimensions and Metrics
This section discusses the metrics and dimensions that Amazon EC2 sends to Amazon CloudWatch, and describes how to enable detailed (one-minute) monitoring for an EC2 instance. Amazon CloudWatch offers basic (five-minute) monitoring for Amazon EC2 by default. To access detailed monitoring of Amazon EC2 instances, you must enable it.
Amazon EC2 Metrics
The following metrics are available from each EC2 instance.
| Metric | Description |
|---|---|
|
The percentage of allocated EC2 compute units that are currently in use on the instance. This metric identifies the processing power required to run an application upon a selected instance. Units: Percent |
|
Completed read operations from all ephemeral disks available to the instance (if your instance uses Amazon EBS, see Amazon EBS Metrics.) This metric identifies the rate at which an application reads a disk. This can be used to determine the speed in which an application reads data from a hard disk. Units: Count |
|
Completed write operations to all ephemeral disks available to the instance (if your instance uses Amazon EBS, see Amazon EBS Metrics.) This metric identifies the rate at which an application writes to a hard disk. This can be used to determine the speed in which an application saves data to a hard disk. Units: Count |
|
Bytes read from all ephemeral disks available to the instance (if your instance uses Amazon EBS, see Amazon EBS Metrics.) This metric is used to determine the volume of the data the application reads from the hard disk of the instance. This can be used to determine the speed of the application. Units: Bytes |
|
Bytes written to all ephemeral disks available to the instance (if your instance uses Amazon EBS, see Amazon EBS Metrics.) This metric is used to determine the volume of the data the application writes onto the hard disk of the instance. This can be used to determine the speed of the application. Units: Bytes |
|
The number of bytes received on all network interfaces by the instance. This metric identifies the volume of incoming network traffic to an application on a single instance. Units: Bytes |
|
The number of bytes sent out on all network interfaces by the instance. This metric identifies the volume of outgoing network traffic to an application on a single instance. Units: Bytes |
Amazon CloudWatch data for a new EC2 instance typically becomes available within one minute of the end of the first period of time requested (the aggregation period) in the query. You can set the period—the length of time over which statistics are aggregated—with the Period parameter. For more information on periods, see Periods.
You can use the currently
available dimensions for EC2 instances (for example, ImageID or InstanceType)
to refine the metrics returned. For information about the dimensions you can
use with EC2, see Dimensions for EC2 Metrics.
Dimensions for EC2 Metrics
EC2 instance data can be filtered using any of the dimensions in the following table.
|
Dimension |
Description |
|---|---|
AutoScalingGroupName
|
This dimension filters the data you request for all instances in a specified capacity group. An AutoScalingGroup is a collection of instances you define if you're using the Auto Scaling service. This dimension is available only for EC2 metrics when the instances are in such an AutoScalingGroup. Available for instances with Detailed or Basic Monitoring enabled. |
ImageId
|
This dimension filters the data you request for all instances running this EC2 Amazon Machine Image (AMI). Available for instances with Detailed Monitoring enabled. |
InstanceId
|
This dimension filters the data you request for the identified instance only. This helps you pinpoint an exact instance from which to monitor data. Available for instances with Detailed Monitoring enabled. |
InstanceType
|
This dimension filters the data you request for all instances running with this specified instance type. This helps you categorize your data by the type of instance running. For example, you might compare data from an m1.small instance and an m1.large instance to determine which has the better business value for your application. Available for instances with Detailed Monitoring enabled. |
Activating Detailed Monitoring for Amazon EC2
The following procedure walks through the steps to enable detailed metric collection for an EC2 instance.
To activate detailed metrics through the console
Sign in to the AWS Management Console and open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
Click the Launch Instance button.
Select an AMI from the list to display the Request Instances Wizard dialog box and configure your EC2 instance.
On the next step of the Request Instances Wizard, click the Enable CloudWatch monitoring for this instance check box.
Continue through the remaining steps of the Request Instances Wizard and click the Launch button.
The instance you launched has detailed monitoring enabled.
Amazon Elastic MapReduce Dimensions and Metrics
This section discusses the metrics and dimensions that Amazon Elastic MapReduce sends to Amazon CloudWatch. All Amazon EMR job flows automatically send metrics in five-minute intervals. Metrics are archived for two weeks; after that period, the data is discarded.
Amazon Elastic MapReduce Metrics
Amazon EMR sends the following metrics to Amazon CloudWatch.
| Note |
|---|---|
Amazon EMR pulls metrics from a job flow. If a job flow becomes unreachable, no metrics will be reported until the job flow becomes available again. |
| Metric | Description |
|---|---|
|
|
The number of core nodes waiting to be assigned. All of the core nodes requested may not be immediately available; this metric reports the pending requests. Data points for this metric are reported only when a corresponding instance group exists. Use Case: Monitor job flow health Units: Count |
|
|
The number of core nodes working. Data points for this metric are reported only when a corresponding instance group exists. Use Case: Monitor job flow health Units: Count |
|
|
The number of bytes read from HDFS. Use Case: Analyze job flow performance, Monitor job flow progress Units: Count |
|
|
The number of bytes written to HDFS. Use Case: Analyze job flow performance, Monitor job flow progress Units: Count |
|
|
The percentage of HDFS storage currently used. Use Case: Analyze job flow performance Units: Percent |
|
|
Indicates that a job flow is no longer performing work, but is still alive and accruing charges. It is set to 1 if no tasks are running and no jobs are running, and set to 0 otherwise. This value is checked at five-minute intervals and a value of 1 indicates only that the job flow was idle when checked, not that it was idle for the entire five minutes. To avoid false positives, you should alarm when this value has been 1 for more than one consecutive 5-minute check. For example, you might raise an alarm on this value if it has been 1 for thirty minutes or longer. Use Case: Monitor job flow performance Units: Count |
|
|
The number of jobs in the job flow that have failed. Use Case: Monitor job flow health Units: Count |
|
|
The number of jobs in the job flow that are currently running. Use Case: Monitor job flow health Units: Count |
|
|
The percentage of data nodes that are receiving work from Hadoop. Use Case: Monitor job flow health Units: Percent |
|
|
The percentage of task trackers that are functional. Use Case: Monitor job flow health Units: Percent |
|
|
The unused map task capacity. This is calculated as the maximum number of map tasks for a given job flow, less the total number of map tasks currently running in that job flow. Use Case: Analyze job flow performance Units: Count |
|
|
The number of blocks in which HDFS has no replicas. These might be corrupt blocks. Use Case: Monitor job flow health Units: Count |
|
|
Unused reduce task capacity. This is calculated as the maximum reduce task capacity for a given job flow, less the number of reduce tasks currently running in that job flow. Use Case: Analyze job flow performance Units: Count |
|
|
The number of remaining map tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs are generated. Use Case: Monitor job flow progress Units: Count |
|
|
The ratio of the total map tasks remaining to the total map slots available in the cluster. Use Case: Analyze job flow performance Units: Ratio |
|
|
The number of remaining reduce tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs will be generated. Use Case: Monitor job flow progress Units: Count |
|
|
The number of running map tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs will be generated. Use Case: Monitor job flow progress Units: Count |
|
|
The number of running reduce tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs will be generated. Use Case: Monitor job flow progress Units: Count |
|
|
The number of bytes read from Amazon S3. Use Case: Analyze job flow performance, Monitor job flow progress Units: Count |
|
|
The number of bytes written to Amazon S3. Use Case: Analyze job flow performance, Monitor job flow progress Units: Count |
|
|
The number of core nodes waiting to be assigned. All of the task nodes requested may not be immediately available; this metric reports the pending requests. Data points for this metric are reported only when a corresponding instance group exists. Use Case: Monitor job flow health Units: Count |
|
|
The number of task nodes working. Data points for this metric are reported only when a corresponding instance group exists. Use Case: Monitor job flow health Units: Count |
|
|
The total number of concurrent data transfers. Use Case: Monitor job flow health Units: Count |
Amazon Elastic MapReduce Metrics
The following dimensions are available for Amazon EMR.
| Dimension | Description |
|---|---|
| JobFlowId |
The identifier for a job flow. You can find this value by clicking on the job flow in the Amazon EMR console.
It takes the form j-XXXXXXXXXXXXX.
|
| JobId | The identifier of a job within a job flow. You can use this to filter the metrics returned from a job flow down to those that apply to a single job within the job flow. JobId takes the form job_XXXXXXXXXXXX_XXXX. |
Amazon RDS Dimensions and Metrics
This section discusses the metrics and dimensions that Amazon Relational Database Service sends to Amazon CloudWatch. Amazon CloudWatch provides detailed monitoring of Amazon RDS by default. Unlike Amazon EC2 and Auto Scaling, you do not need to specifically enable detailed monitoring.
Amazon RDS Metrics
The following metrics are available from Amazon Relational Database Service.
| Metric | Description |
|---|---|
BinLogDiskUsage |
The amount of disk space occupied by binary logs on the master. Units: Bytes |
CPUUtilization |
The percentage of CPU utilization. Units: Percent |
DatabaseConnections |
The number of database connections in use. Units: Count |
FreeableMemory |
The amount of available random access memory. Units: Bytes |
FreeStorageSpace |
The amount of available storage space. Units: Bytes |
ReplicaLag |
The amount of time a Read Replica DB Instance lags behind the source DB Instance. Units: Seconds |
SwapUsage |
The amount of swap space used on the DB Instance. Units: Bytes |
ReadIOPS |
The average number of disk I/O operations per second. Units: Count/Second |
WriteIOPS |
The average number of disk I/O operations per second. Units: Count/Second |
ReadLatency |
The average amount of time taken per disk I/O operation. Units: Seconds |
WriteLatency |
The average amount of time taken per disk I/O operation. Units: Seconds |
ReadThroughput |
The average number of bytes read from disk per second. Units: Bytes/Second |
WriteThroughput |
The average number of bytes written to disk per second. Units: Bytes/Second |
Dimensions for RDS Metrics
Amazon RDS data can be filtered along any of the following dimensions in the table below.
|
Dimension |
Description |
|---|---|
DBInstanceIdentifier
|
This dimension filters the data you request for a specific database instance. |
DatabaseClass
|
This dimension filters the data you request for all instances in a database class.
For example, you can aggregate metrics for all instances that
belong to the database class |
EngineName
|
This dimension filters the data you request for the identified engine name only.
For example, you can aggregate metrics for all instances that have the engine name
|
Amazon SNS Dimensions and Metrics
Amazon SNS sends data points to Amazon CloudWatch for several metrics. All active topics automatically send five-minute metrics to Amazon CloudWatch. Detailed monitoring, or one-minute metrics, is currently unavailable for Amazon SNS. A topic stays active for six hours from the last activity (i.e. any API call) on the topic.
Amazon SNS Metrics
This section discusses the metrics that Amazon Simple Notification Service (Amazon SNS) sends to Amazon CloudWatch.
| Metric | Description |
|---|---|
|
The number of messages published to the topic. Units: Count Valid Statistics: Sum |
|
The size of messages published to the topic. Units: Bytes Valid Statistics: Minimum, Maximum, Average and Count |
|
The number of messages successfully delivered to all subscriptions of the topic. Units: Count Valid Statistics: Sum |
|
The number of all notification attempts to the topic that failed delivery. Units: Count Valid Statistics: Sum |
Amazon SQS Dimensions and Metrics
Amazon SQS sends data points to Amazon CloudWatch for several metrics. All active queues automatically send five-minute metrics to Amazon CloudWatch. Detailed monitoring, or one-minute metrics, is currently unavailable for Amazon SQS. A queue stays active for six hours from the last activity (i.e. any API call) on the queue.
Amazon SQS Metrics
This section discusses the metrics that Amazon Simple Queue Service (Amazon SQS) sends to Amazon CloudWatch.
| Metric | Description |
|---|---|
|
The number of messages added to a queue. Units: Count Valid Statistics: Sum |
|
The size of messages added to a queue. Units: Bytes Valid Statistics: Minimum, Maximum, Average and Count |
|
The number of messages returned by calls to the Units: Count Valid Statistics: Sum |
|
The number of Units: Count Valid Statistics: Sum |
|
The number of messages deleted from the queue. Units: Count Valid Statistics: Sum |
|
The number of messages in the queue that are delayed and not available for reading immediately. This can happen when the queue is configured as a delay queue or when a message has been sent with a delay parameter. Units: Count Valid Statistics: Average |
|
The number of messages available for retrieval from the queue. Units: Count Valid Statistics: Average |
|
The number of messages that are in flight. Messages are considered in flight if they have been sent to a client but have not yet been deleted or have not yet reached the end of their visibility window. Units: Count Valid Statistics: Average |
AWS Storage Gateway Dimensions and Metrics
AWS Storage Gateway sends data points to Amazon CloudWatch for several metrics. All active queues automatically send five-minute metrics to Amazon CloudWatch. Detailed monitoring, or one-minute metrics, is currently unavailable for AWS Storage Gateway.
AWS Storage Gateway Metrics
The following metrics are available from the AWS Storage Gateway Service.
The following table describes the AWS Storage Gateway metrics that you can use to get
information about your gateways. Specify the GatewayId or
GatewayName dimension for each metric to view the data for a
gateway.
| Metric | Description |
|---|---|
ReadBytes
|
The total number of bytes read from your on-premises applications in the reporting period for all volumes in the gateway. Use this metric to measure throughput by selecting the Units: Bytes |
WriteBytes |
The total number of bytes written to your on-premises applications in the reporting period for all volumes in the gateway. Use this metric to measure throughput by selecting the Units: Bytes |
ReadTime |
The total number of milliseconds spent to do reads from your on-premises applications in the reporting period for all volumes in the gateway. Use this metric with the Units: Milliseconds |
WriteTime |
The total number of milliseconds spent to do writes from your on-premises applications in the reporting period for all volumes in the gateway. Use this metric with the Units: Milliseconds |
QueuedWrites |
The number of bytes waiting to be written to AWS, sampled at the end of the reporting period for all volumes in the gateway. These bytes are kept in your gateway's working storage. Units: Bytes |
CloudBytesDownloaded |
The total number of bytes that the gateway downloaded from AWS during the reporting period. Use this metric to measure throughput by selecting the Units: Bytes |
CloudBytesUploaded |
The total number of bytes that the gateway uploaded to AWS during the reporting period. Use this metric to measure throughput by selecting the Units: Bytes |
CloudDownloadLatency |
The total number of milliseconds spent reading data from AWS during the reporting period. Use this metric with the Units: Milliseconds |
WorkingStoragePercentUsed |
Percent utilization of the gateway's working storage. The sample is taken at the end of the reporting period. Units: Percent |
WorkingStorageUsed |
The total number of bytes being used in the gateway's working storage. The sample is taken at the end of the reporting period. Units: Bytes |
WorkingStorageFree |
The total amount of unused space in the gateway's working storage. The sample is taken at the end of the reporting period. Units: Bytes |
The following table describes the AWS Storage Gateway metrics that you can use to get
information about your storage volumes. Specify the VolumeId dimension for
each metric to view the data for a storage volume.
| Metric | Description |
|---|---|
ReadBytes
|
The total number of bytes read from your on-premises applications in the reporting period. Use this metric to measure throughput by selecting the Units: Bytes |
WriteBytes |
The total number of bytes written to your on-premises applications in the reporting period. Use this metric to measure throughput by selecting the Units: Bytes |
ReadTime |
The total number of milliseconds spent to do reads from your on-premises applications in the reporting period. Use this metric with the Units: Milliseconds |
WriteTime |
The total number of milliseconds spent to do writes from your on-premises applications in the reporting period. Use this metric with the Units: Milliseconds |
QueuedWrites |
The number of bytes waiting to be written to AWS, sampled at the end of the reporting period. Units: Bytes |
Dimensions for AWS Storage Gateway Metrics
The Amazon CloudWatch namespace for the service is
AWS/StorageGateway. Data is available automatically in 5-minute periods
at no charge.
|
Dimension |
Description |
|---|---|
GatewayId, GatewayName |
These dimensions filter the data you request to gateway-specific
metrics. You can identify a gateway to work by its
Throughput and latency data of a gateway is based on all the volumes for the gateway. For information about working with gateway metrics, see Measuring Performance Between Your Gateway and AWS. |
VolumeId
|
This dimension filters the data you request to
volume-specific metrics. Identify a storage
volume to work with by its |
Auto Scaling Dimensions and Metrics
This section discusses the metrics that Auto Scaling instances and groups send to Amazon CloudWatch and describes how to enable detailed (one-minute) monitoring and basic (five-minute) monitoring.
Auto Scaling Instance Support
This section discusses the metrics that Auto Scaling instances send to Amazon CloudWatch. Instance metrics are the metrics that an individual Amazon EC2 instance sends to Amazon CloudWatch. Instance metrics are the same metrics available for any Amazon EC2 instance, whether or not it is in an Auto Scaling group.
Amazon CloudWatch offers basic or detailed monitoring. Basic monitoring sends aggregated data about each instance to Amazon CloudWatch every five minutes. Detailed monitoring offers more frequent aggregated data by sending data from each instance every minute.
| Note |
|---|---|
Selecting detailed monitoring is a prerequisite for the collection of Auto Scaling group metrics. For more information, see Auto Scaling Group Support. |
The following sections describe how to enable either detailed monitoring or basic monitoring.
Activating Detailed Instance Monitoring for Auto Scaling
To enable detailed instance monitoring for a new Auto Scaling group, you don't need to take any extra steps.
One of your first steps when creating an Auto Scaling group is to create a launch configuration.
Each launch configuration contains a flag named InstanceMonitoring.Enabled.
The default value of this flag is true,
so you don't need to set this flag if you want detailed monitoring.
If you have an Auto Scaling group for which you have explicitly selected basic monitoring, the switch to detailed monitoring involves several steps, especially if you have Amazon CloudWatch alarms configured to scale the group automatically.
To switch to detailed instance monitoring for an existing Auto Scaling group
Create a launch configuration that has the
InstanceMonitoring.Enabledflag enabled. If you are using the command line tools, create a launch configuration with the--monitoring-enabledoption.Call
UpdateAutoScalingGroupto update your Auto Scaling group with the launch configuration you created in the previous step. Auto Scaling will enable detailed monitoring for new instances that it creates.Choose one of the following actions to deal with all existing Amazon EC2 instances in the Auto Scaling group:
To... Do This... Preserve existing instances Call MonitorInstancesfrom the Amazon EC2 API for each existing instance to enable detailed monitoring.Terminate existing instances Call TerminateInstanceInAutoScalingGroupfrom the Auto Scaling API for each existing instance. Auto Scaling will use the updated launch configuration to create replacement instances with detailed monitoring enabled.If you have Amazon CloudWatch alarms associated with your Auto Scaling group, call
PutMetricAlarmfrom the Amazon CloudWatch API to update each alarm so that the alarm's period value is set to 60 seconds.
Activating Basic Instance Monitoring for Auto Scaling
To create a new Auto Scaling group with basic monitoring instead of detailed monitoring,
associate your new Auto Scaling group with a launch configuration that has the
InstanceMonitoring.Enabled flag set to false.
If you are using the command line tools, create a launch
configuration with the --monitoring-disabled option.
To switch to basic instance monitoring for an existing Auto Scaling group
Create a launch configuration that has the
InstanceMonitoring.Enabledflag disabled. If you are using the command line tools, create a launch configuration with the--monitoring-disabledoption.If you previously enabled group metrics with a call to
EnableMetricsCollection, callDisableMetricsCollectionon your Auto Scaling group to disable collection of all group metrics. For more information, see Auto Scaling Group Support.Call
UpdateAutoScalingGroupto update your Auto Scaling group with the launch configuration you created in the previous step. Auto Scaling will disable detailed monitoring for new instances that it creates.Choose one of the following actions to deal with all existing Amazon EC2 instances in the Auto Scaling group:
To... Do This... Preserve existing instances Call UnmonitorInstancesfrom the Amazon EC2 API for each existing instance to disable detailed monitoring.Terminate existing instances Call TerminateInstanceInAutoScalingGroupfrom the Auto Scaling API for each existing instance. Auto Scaling will use the updated launch configuration to create replacement instances with detailed monitoring disabled.If you have Amazon CloudWatch alarms associated with your Auto Scaling group, call
PutMetricAlarmfrom the Amazon CloudWatch API to update each alarm so that the alarm's period value is set to 300 seconds.![[Important]](http://docs.amazonwebservices.com/docs-common/images/important.png)
Important If you do not update your alarms to match the five-minute data aggregations, your alarms will continue to check for statistics every minute and might find no data available for as many as four out of every five periods.
For more information on instance metrics for Amazon EC2 instances, see Amazon EC2 Dimensions and Metrics.
Auto Scaling Group Support
Group metrics are metrics that an Auto Scaling group sends to Amazon CloudWatch to describe the group rather than any of its instances. If you enable group metrics, Auto Scaling sends aggregated data to Amazon CloudWatch every minute. If you disable group metrics, Auto Scaling does not send any group metrics data to Amazon CloudWatch.
To enable group metrics
Enable detailed instance monitoring for the Auto Scaling group by setting the
InstanceMonitoring.Enabledflag in the Auto Scaling group's launch configuration. For more information, see Auto Scaling Instance Support.Call
EnableMetricsCollection, which is part of the Auto Scaling Query API. Alternatively, you can use the equivalentas-enable-metrics-collectioncommand that is part of the Auto Scaling command line tools.
Auto Scaling group metrics table
You may enable or disable each of the following metrics, separately.
| Metric | Description |
|---|---|
GroupMinSize |
The minimum size of the Auto Scaling group. Units: Count |
GroupMaxSize |
The maximum size of the Auto Scaling group. Units: Count |
GroupDesiredCapacity |
The number of instances that the Auto Scaling group attempts to maintain. Units: Count |
GroupInServiceInstances |
The number of instances that are running as part of the Auto Scaling group. This metric does not include instances that are pending or terminating. Units: Count |
GroupPendingInstances |
The number of instances that are pending. A pending instance is not yet in service. This metric does not include instances that are in service or terminating. Units: Count |
GroupTerminatingInstances |
The number of instances that are in the process of terminating. This metric does not include instances that are in service or pending. Units: Count |
GroupTotalInstances |
The total number of instances in the Auto Scaling group. This metric identifies the number of instances that are in service, pending, and terminating. Units: Count |
Elastic Load Balancing Dimensions and Metrics
This section discusses the metrics and dimensions that Elastic Load Balancing sends to Amazon CloudWatch. Amazon CloudWatch provides detailed monitoring of Elastic Load Balancing by default. Unlike Amazon EC2, you do not need to specifically enable detailed monitoring.
| Note |
|---|---|
Elastic Load Balancing only emits Amazon CloudWatch metrics when requests are flowing through the load balancer. |
Elastic Load Balancing Metrics
The following Elastic Load Balancing metrics are available from Amazon CloudWatch.
The HTTP response code metrics reflect the count of Elastic Load Balancing response codes that are sent to clients within a given time period. If no response codes in the category 2XX-5XX range are sent to clients within the given time period, values for these metrics will not be recorded in CloudWatch.
| Metric | Description |
|---|---|
Latency |
Time elapsed after the load balancer receives a request until it receives the corresponding response. Units: Seconds Valid Statistics: Minimum, Maximum, Average, and Count |
RequestCount |
The number of requests handled by the load balancer. Units: Count Valid Statistics: Sum |
HealthyHostCount |
The number of healthy Amazon EC2 instances registered with the
load balancer in a specified Availability Zone. Hosts that have not
failed more health checks than the value of the unhealthy threshold are
considered healthy. When evaluating this metric, the dimensions must be
provided for Units: Count Valid Statistics: Minimum, Maximum, and Average |
UnHealthyHostCount |
The number of unhealthy Amazon EC2 instances registered with the
load balancer in a specified Availability Zone. Hosts that have failed
more health checks than the value of the unhealthy threshold are
considered unhealthy. When evaluating this metric, the dimensions must
be provided for Units: Count Valid Statistics: Minimum, Maximum, and Average |
HTTPCode_ELB_4XX |
Count of HTTP response codes generated by Elastic Load Balancing that are in the 4xx (client error) series. Units: Count Valid Statistics: Sum |
HTTPCode_ELB_5XX |
Count of HTTP response codes generated by Elastic Load Balancing that are in the 5xx (server error) series. Elastic Load Balancing may generate 5xx errors if no back-end instances are registered, no healthy back-end instances, or the request rate exceeds Elastic Load Balancing’s current available capacity. Units: Count Valid Statistics: Sum |
HTTPCode_Backend_2XX |
Count of HTTP response codes generated by back-end instances that are in the 2xx (success) series. Units: Count Valid Statistics: Sum |
HTTPCode_Backend_3XX |
Count of HTTP response codes generated by back-end instances that are in the 3xx (user action required) series. Units: Count Valid Statistics: Sum |
HTTPCode_Backend_4XX |
Count of HTTP response codes generated by back-end instances that are in the 4xx (client error) series. This response count does not include any responses that were generated by Elastic Load Balancing. Units: Count Valid Statistics: Sum |
HTTPCode_Backend_5XX |
Count of HTTP response codes generated by back-end instances that are in the 5xx (server error) series. This response count does not include any responses that were generated by Elastic Load Balancing. Units: Count Valid Statistics: Sum |
Dimensions for Elastic Load Balancing Metrics
You can use the currently available dimensions for Elastic Load Balancing to refine the metrics returned by a query. For example, you could use HealthyHostCount and dimensions LoadBalancerName and AvailabilityZone to get the Average number of healthy Instances behind the specified LoadBalancer within the specified Availability Zone for a given period of time.
Elastic Load Balancing data can be aggregated along any of the following dimensions shown in the table below.
|
Dimension |
Description |
|---|---|
LoadBalancerName
|
Limits the metric data to Amazon EC2 instances that are connected to the specified load balancer. |
AvailabilityZone
|
Limits the metric data to load balancers in the specified Availability Zone. |
