-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Metricbeat] Update cloudwatch metricset mappings #15245
[Metricbeat] Update cloudwatch metricset mappings #15245
Conversation
AWS cloudwatch metrics were being reported under `aws.metrics`, but the mapping definitions in `fields.yml` were expecting these under `aws.cloudwatch.metrics`. This change fixes that and refactors how metrics are handled when used together with Lightweight modules. Metrics should now include the metricset name in the path, example: For cloudwatch metricset, metrics look like: ``` aws.cloudwatch.metrics.CPUUtilization.p10 aws.cloudwatch.dimensions.InstanceId ``` While when used from a lightweight module it produces: ``` aws.ebs.metrics.BurstBalance.avg aws.cloudwatch.dimensions.VolumeId ``` I kept dimensions together as sometimes these can be used for correlation, so having them under the same field helps.
Tried to change mapping to
I got error:
If we use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking this! I think metrics look now much better, the change should make them easier to discover 🎉
@exekias I updated all the data.json files and dashboards. This is ready for review. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add a message into the breaking changes section of the CHANGELOG?
Also I guess existing PRs using cloudwatch will need to rebase
@exekias The current changelog entry is already under breaking changes - metricbeat. Yes, two PRs for adding new aws metricset are waiting for this PR to get in first. |
Ouch I'm blind 🙈, then 👍 to |
This PR is to continue working on #14653 to update mappings in cloudwatch metrics and all the metricsets that are created using light module based on cloudwatch metricset.
Mapping change:
aws.cloudwatch.metrics.BurstBalance.avg
->aws.ebs.metrics.BurstBalance.avg
aws.cloudwatch.dimensions.VolumeId
->aws.dimensions.VolumeId
TODO - fix dashboards:
TODO - regenerate data.json files in metricsets:
How to test this
Make sure the AWS account you use for testing has multiple different services. Enalbe aws metricbeat module and modify aws.yml with: