Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[AWS] Dashboards are using wrong field names #3703

@kaiyan-sheng

Description

@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.

screenshot_2022-07-12_at_14 59 08

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions