Blue Matador will automatically detect any Elastic Beanstalk environments in your AWS account and monitor them. However, Elastic Beanstalk does not always expose all of the CloudWatch metrics that Blue Matador monitors, so enhanced health reporting is required to be configured so that Blue Matador can fully monitor your environments.
What Blue Matador Uses
The following is a list of enhanced monitoring features that Blue Matador uses to monitor Elastic Beanstalk:
- Environment Health Status
- CloudWatch Custom Metric (Environment): ApplicationRequestsTotal
- CloudWatch Custom Metric (Environment): ApplicationLatencyP99
- CloudWatch Custom Metric (Instance): LoadAverage1min
- CloudWatch Custom Metric (Instance): RootFilesystemUtil
- Enhanced Events
Enabling Enhanced Health Reporting
Follow the AWS documentation to enable enhanced health reporting on each Elastic Beanstalk environment that Blue Matador should fully monitor. When selecting the CloudWatch Custom Metrics to configure, ensure that both the ApplicationRequestsTotal and ApplicationLatencyP99 metric are selected in the list under Environment, and that the LoadAverage1min and RootFilesystemUtil metrics are selected under Instance. Don’t forget to click Apply so your changes are propagated throughout your environment.
Basic Health Reporting
Without enhanced health reporting enabled, the only data Blue Matador can collect for an environment is the basic Events reported by Elastic Beanstalk.