When enhanced health reporting for Amazon Elastic Beanstalk is enabled, Blue Matador detects anomalies in the ApplicationRequestsTotal and ApplicationLatencyP99 CloudWatch metrics.

Application Requests

Most Beanstalk environments will see a pretty consistent pattern of requests. When Blue Matador detects a recent spike or drop in the ApplicationRequestsTotal metric that is not consistent with your environment, an anomaly will be created. Possible causes of changes in request count include:

  • Errors in your server side code causing retry logic in your clients to make many requests to a failing endpoint
  • A release of buggy client code causing erroneous API requests
  • A malfunctioning cache layer


Application Latency

While Beanstalk exposes multiple CloudWatch metrics to track latency, Blue Matador detects anomalies in the ApplicationLatencyP99 metric. This ensures that the most requests get considered in the latency calculation while leaving room for the occasional slow endpoint. An increase in latency can indicate a performance issue with your application. If traffic patterns for your application have not changed significantly, check to see if a downstream service such as a database or SQS is experiencing high latency, and propagating that time to your web server. If you have seen an increase in traffic, it is possible that your instances are overloaded and adding capacity to the application may help.