-
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
AWS Metricbeat Module #10115
Comments
One enhancement issue: #11820 |
Adding tags support in AWS module: #12263 |
Hi @kaiyan-sheng, I don't know if this is the right place to ask questions, but I'm very interested in the AWS module especially for EC2 metrics, this is a really cool feature! My question is: Is there any way to collect only selected metrics and get them only for a subset of my ec2 instances running in a region? Would be great filter them by tags or name. Should I open an issue for that? Thanks! |
Hi @Giaco9, thanks for reaching out! If you only want to collect metrics from a specific region, then you can use
If you want to specify both ec2 instances and regions, then you can try
For ec2 metricset, tags will be collected by default so if you have tags for the instances you are interested, you can also collect all metrics and then filter by tags in Kibana for visualization. |
This is a meta issue to track the work on adding AWS metricbeat module including varies metricsets.
This checklist is intended for Devs which create or update a module to make sure modules are consistent.
The text was updated successfully, but these errors were encountered: