[AWS] Dashboards are using wrong field names

[kaiyan-sheng]

Some visualization fields are referenced that don't exist in the actual data in AWS integration. For example in the "Cloudwatch Lambda Errors Top5" visualization, it is referencing the field aws.lambda.metrics.Errors, but this field doesn't exist. We should be using aws.lambda.metrics.Errors.avg instead. Similarly, we are using aws.lambda.metrics.Throttles in the dashboard as well.

Similar problem: for elb,aws.elb.metrics.RequestCount in the vis vs aws.elb.metrics.RequestCount.sum in the documentation and in the index template. Cloudwatch Memory Available [Metrics AWS] is using multiple fields such as aws.ecs.metrics.MemoryUlitization which does not exist. Also same problem with the fields starting with aws.metworkfirewall.metrics.

[botelastic]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!