-
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 ability to collect tags for aws services #12263
Labels
Comments
+1 to having this. Just a note, as tags are also present in other AWS resources, it could make sense to use |
Yes, good point! We can start with adding tags for EC2 and then expand to other resources. Thanks! |
+1 large customer is requesting as well |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Quote from AWS documentation:
A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value, both of which you define. Tags enable you to categorize your AWS resources in different ways, for example, by purpose, owner, or environment. This is useful when you have many resources of the same type—you can quickly identify a specific resource based on the tags you've assigned to it. For example, you could define a set of tags for your account's Amazon EC2 instances that helps you track each instance's owner and stack level.
Adding the ability to collect tags for AWS ec2 metricset, will give users the flexibility to query/filter on tags for better monitoring each instance. Tags can be a part of the metadata in ec2 metricset under field
aws.ec2.instance.tags.*
and this will be only available forec2
metricset. If users usecloudwatch
metricset to collect EC2 monitoring metrics, then there will be no tags included.The text was updated successfully, but these errors were encountered: