-
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] Add dedot to aws ec2 metricset and cloudwatch metricset #15844
Conversation
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.
LGTM, but wondering what would happen if there is no DeDot option and it's a default behavior, so the end user can't disable it.
Yep, I just had a talk with Carlos and we think it's good to remove the config option and just enable it by default. |
…etricset and cloudwatch metricset (elastic#15896) * [Metricbeat] Add dedot to aws ec2 metricset and cloudwatch metricset (elastic#15844) * Add dedot to aws ec2 metricset and cloudwatch metricset * Remove dedot config parameter (cherry picked from commit 65dbf15)
What does this PR do?
This PR is to add dedot to ec2 and cloudwatch metricset in aws module.
Why is it important?
If a tag key includes dot, then ec2 metricset will fail with error like:
With this PR, you will be able to see events for EC2 instances that have tags with dot. For example:
Checklist
How to test this PR locally
Create an EC2 instance and add a set of tag with dot in there. For example:
app.kubernetes.io/name = foo
Then start Metricbeat aws module with aws.yml:
Then you should see tags collected by aws module in events. Tag name should be
aws.tags.app_kubernetes_io/name
with valuefoo
.Related issues