Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

ELB metrics not found in CloudWatch

I have a load balancer in ap-northeast-1 (Tokyo) region.

According to this article, I think I should be able to find Backend Connection Errors, Surge Queue Length, and Spillovers metrics in CloudWatch. But I can't find them.

Are these metrics only available in specific regions?

I've googled for hours but failed to find an answer.

Currently I can see 15 metric for my ELB, which are

  1. Average Latency

  2. Sum Requests

  3. Sum HTTP 5XXs

  4. Sum HTTP 4XXs

  5. Sum ELB 5XXs

  6. Sum ELB 4XXs

  7. Target connection errors

  8. Sum rejected connections

  9. Target TLS Negotiation Errors

  10. Sum HTTP 3XXs

  11. Sum HTTP 3XXs

  12. Sum HTTP 2XXs

  13. Active Connection Count

  14. New Connection Count

  15. Processed Bytes

like image 697
Brian Avatar asked Nov 18 '16 03:11

Brian


People also ask

How do I enable CloudWatch metrics?

Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ . In the navigation pane, choose Instances. Select the instance and choose Actions, CloudWatch Monitoring, Enable Detailed Monitoring. In the Enable Detailed Monitoring dialog box, choose Yes, Enable.

How long does it take for CloudWatch metrics to appear?

However, it can take up to 15 minutes before the new metric appears in the list of metrics retrieved using the list-metrics command. Although you can publish data points with time stamps as granular as one-thousandth of a second, CloudWatch aggregates the data to a minimum granularity of 1 second.


1 Answers

The AWS documentation lists:

  • CloudWatch Metrics for Your Classic Load Balancer
  • CloudWatch Metrics for Your Application Load Balancer

The Classic list includes:

  • BackendConnectionErrors: The number of connections that were not successfully established between the load balancer and the registered instances.
  • SurgeQueueLength: The total number of requests that are pending routing.
  • SpilloverCount: The total number of requests that were rejected because the surge queue is full.

If these metrics are not appearing, it may be because the values are zero. Typically, zero values are not sent to Amazon CloudWatch.

like image 186
John Rotenstein Avatar answered Oct 05 '22 21:10

John Rotenstein