Specifications for ELB metrics integrated with AWS Integration have changed

Using the CloudWatch API to obtain ELB (CLB / ALB) metrics in relation to each HTTP status response count (e.g. HTTP Code ELB Count), responses without metric points themselves can be obtained at times when there is no response such as 4xx or 5xx.

Mackerel’s AWS integration also followed the CloudWatch API response, but was incompatible with Mackerel’s specifications and we received inquiries from multiple customers about a problem with monitoring not starting unless metric points existed. With this release, if there is no metric points, ELB metrics in relation to the response count for each HTTP status are now registered as 0.

This makes checking graphs more intuitive and also resolves the problem in the past where target metrics could not be selected if there were no 4xx or 5xx responses.

Updates for mackerel-agent-plugins and more

In addition to the updates made for go-check-plugins above, the following items have also been updated.