AWS Plugin services

Number of requests where the load balancer removed HTTP headers with header fields that are not valid before routing the request.

The load balancer removes these headers only if the routing.http.drop_invalid_<br>header_fields.enabled attribute is set to true.

Number of requests routed by the load balancer that had HTTP headers with header fields that are not valid.

The load balancer forwards requests with these headers only if the routing.http.drop_invalid_<br>header_fields.enabled attribute is set to false.

Number of requests where the load balancer chose a new target because it couldn’t use an existing sticky session.

For example, the request was the first request from a new client and no stickiness cookie was presented, a stickiness cookie was presented but it did not specify a target that was registered with this target group, the stickiness cookie was malformed or expired, or an internal error prevented the load balancer from reading the stickiness cookie.

Total number of bytes processed by the load balancer over IPv4 and IPv6.

This count includes traffic to and from clients and Lambda functions, and traffic from an Identity Provider (IdP) if user authentication is enabled.

Number of requests processed over IPv4 and IPv6.

This metric is only incremented for requests where the load balancer node was able to choose a target. Requests rejected before a target is chosen (for example, HTTP 460, HTTP 400, some kinds of HTTP 503 and 500) are not reflected in this metric.

Average number of requests received by each target in a target group.

You must specify the target group using the TargetGroup dimension. This metric does not apply if the target is a Lambda function.

Number of connections that were not successfully established between the load balancer and target.

This metric does not apply if the target is a Lambda function.

Number of TLS connections initiated by the load balancer that did not establish a session with the target.

Possible causes include a mismatch of ciphers or protocols. This metric does not apply if the target is a Lambda function.

Indicates whether the certificate is in use by another AWS service.

Possible values are Yes or No.

Number of failed attempts to perform conditional writes. The PutItem, UpdateItem, and DeleteItem operations let you provide a logical condition that must evaluate to true before the operation can proceed.

If this condition evaluates to false, the ConditionalCheckFailedRequests is incremented by one. ConditionalCheckFailedRequests is also incremented by one for PartiQL Update and Delete statements where a logical condition is provided and that condition evaluates to false.

Number of read capacity units consumed over the specified time period, so you can track how much of your provisioned throughput is used.

You can retrieve the total consumed read capacity for a table and all of its global secondary indexes, or for a particular global secondary index.

Number of write capacity units consumed over the specified time period, so you can track how much of your provisioned throughput is used.

You can retrieve the total consumed write capacity for a table and all of its global secondary indexes, or for a particular global secondary index.

Number of write capacity units consumed when adding a new global secondary index to a table. If the write capacity of the index is too low, the incoming write activity during the backfill phase might be throttled. This can increase the time it takes to create the index.

You should monitor this statistic while the index is being built to determine whether the write capacity of the index is underprovisioned.

Percentage of completion when a new global secondary index is being added to a table. DynamoDB must first allocate resources for the new index, and then backfill attributes from the table into the index. For large tables, this process might take a long time.

You should monitor this statistic to view the relative progress as DynamoDB builds the index.

Requests to DynamoDB that exceed the provisioned throughput limits on a resource (such as a table or an index).

ThrottledRequests is incremented by one if any event within a request exceeds a provisioned throughput limit. For example, if you update an item in a table with global secondary indexes, there are multiple events—a write to the table, and a write to each index. If one or more of these events are throttled, then ThrottledRequests is incremented by one.

Number of earned CPU credits that an instance has accrued since it was launched or started.

For T2 Standard, the CPUCreditBalance also includes the number of launch credits that have been accrued.

Percentage of the allocated EC2 compute units that are currently in use on the instance.

This metric identifies the processing power required to run an application on a selected instance.

Number of bytes received by the instance on all network interfaces.

This metric identifies the volume of incoming network traffic to a single instance.

Number of bytes sent out by the instance on all network interfaces.

This metric identifies the volume of outgoing network traffic from a single instance.

Number of packets received by the instance on all network interfaces.

This metric identifies the volume of incoming traffic in terms of the number of packets on a single instance.

Number of packets sent out by the instance on all network interfaces.

This metric identifies the volume of outgoing traffic in terms of the number of packets on a single instance.

For Redis, this is the number of client connections, excluding connections from read replicas.

For Memcached, this is a count of the number of connections connected to the cache at an instant in time.

For Redis, this is the number of keys that have been evicted due to the maxmemory limit.

For Memcached, this is the number of non-expired items the cache evicted to allow space for new writes.

For Redis, this is the total number of connections that have been accepted by the server during this period.

For Memcached, this is the number of new connections the cache has received.

For Redis, this is the total number of key expiration events.

For Memcached, this is the number of expired items the cache evicted to allow space for new writes.

This metric is only applicable for a node running as a read replica.

It represents how far behind, in seconds, the replica is in applying changes from the primary node.

Current state of this cluster.

Possible values: available, creating, deleted, deleting, incompatible-network, modifying, rebooting cluster nodes, restore-failed, or snapshotting.

Number of connections that were not successfully established between the load balancer and the registered instances.

Since the load balancer retries the connection when there are errors, this count can exceed the request rate. Note that this count also includes any connection errors related to health checks.

Number of healthy instances registered with the load balancer.

A newly registered instance is considered healthy after it passes the first health check. If cross-zone load balancing is enabled, the number of healthy instances for the LoadBalancerName dimension is calculated across all Availability Zones. Otherwise, it is calculated per Availability Zone.

HTTP listener: Number of HTTP 2XX response codes generated by registered instances.

This count does not include any response codes generated by the load balancer.

HTTP listener: Number of HTTP 3XX response codes generated by registered instances.

This count does not include any response codes generated by the load balancer.

HTTP listener: Number of HTTP 4XX response codes generated by registered instances.

This count does not include any response codes generated by the load balancer.

HTTP listener: Number of HTTP 5XX response codes generated by registered instances.

This count does not include any response codes generated by the load balancer.

HTTP listener: Number of HTTP 4XX client error codes generated by the load balancer.

Client errors are generated when a request is malformed or incomplete.

HTTP listener: Number of HTTP 5XX server error codes generated by the load balancer.

This count does not include any response codes generated by the registered instances. The metric is reported if there are no healthy instances registered to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.

HTTP listener: Total time elapsed, in seconds, from the time the load balancer sent the request to a registered instance until the instance started to send the response headers.

TCP listener: Total time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.

Number of requests completed or connections made during the specified interval (1 or 5 minutes).

HTTP listener: Number of requests received and routed, including HTTP error responses from the registered instances.

TCP listener: Number of connections made to the registered instances.

Total number of requests that were rejected because the surge queue is full.

HTTP listener: Load balancer returns an HTTP 503 error code.

TCP listener: Load balancer closes the connection.

Total number of requests (HTTP listener) or connections (TCP listener) that are pending routing to a healthy instance.

The maximum size of the queue is 1024. Additional requests or connections are rejected when the queue is full. For more information, see, spillover_count.

Number of unhealthy instances registered with your load balancer.

An instance is considered unhealthy after it exceeds the unhealthy threshold configured for health checks. An unhealthy instance is considered healthy again after it meets the healthy threshold configured for health checks.

Number of times a rule’s target is not invoked in response to an event.

This includes invocations that would result in running the same rule again, causing an infinite loop.

Number of invocations that failed permanently.

This does not include invocations that are retried or invocations that succeeded after a retry attempt.

It also does not count failed invocations that are counted in DeadLetterInvocations.

Number of times a target is invoked by a rule in response to an event.

This includes successful and failed invocations, but does not include throttled or retried attempts until they fail permanently. It does not include DeadLetterInvocations.

EventBridge only sends this metric to CloudWatch if it is not zero.

Number of invocations that cannot be moved to a dead-letter queue.

Dead-letter queue errors occur due to permissions errors, unavailable resources, or size limits. EventBridge only sends this metric to CloudWatch if it isn’t zero.

Number of invocations that are moved to a dead-letter queue.

EventBridge only sends this metric to CloudWatch if it is not zero.

Number of rules that have run and matched with any event.

You cannot see this metric in CloudWatch until a rule is triggered.

Age of the last record in all GetRecords calls made against a Kinesis stream, measured over the specified time period.

Age is the difference between the current time and when the last record of the GetRecords call was written to the stream. A value of zero indicates that the records being read are completely caught up with the stream.

Age of the last record in all GetRecords calls made against a shard, measured over the specified time period.

Age is the difference between the current time and when the last record of the GetRecords call was written to the stream.

Number of bytes received from the shard, measured over the specified time period.

Minimum, Maximum, and Average statistics represent the bytes published in a single event for the specified time period.

Number of records received from the shard, measured over the specified time period.

Minimum, Maximum, and Average statistics represent the records in a single event for the specified time period.

Number of records rejected due to throttling for the stream over the specified time period.

This metric includes throttling from PutRecord and PutRecords operations. The most commonly used statistic for this metric is Average.

T2 instances: Number of earned CPU credits that an instance has accrued since it was launched or started.

For T2 Standard, the CPUCreditBalance also includes the number of launch credits that have been accrued.

Number of messages that were rejected by subscription filter policies.

A filter policy rejects a message when the message attributes do not match the policy attributes.

Bytes received on the AWS side of the connection through the VPN tunnel from a customer gateway.

Each metric data point represents the number of bytes received after the previous data point.

Bytes sent from the AWS side of the connection through the VPN tunnel to the customer gateway.

Each metric data point represents the number of bytes sent after the previous data point.

State of the tunnels.

For static VPNs, 0 indicates DOWN, while 1 indicates UP.

For BGP VPNs, 1 indicates ESTABLISHED, while 0 is used for all other states.

For both types of VPNs, values between 0 and 1 indicate at least one tunnel is not UP.