Skip to content
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

Closed
7 tasks done
kaiyan-sheng opened this issue Jan 16, 2019 · 5 comments
Closed
7 tasks done

AWS Metricbeat Module #10115

kaiyan-sheng opened this issue Jan 16, 2019 · 5 comments
Assignees
Labels
meta Metricbeat Metricbeat module Team:Integrations Label for the Integrations team

Comments

@kaiyan-sheng
Copy link
Contributor

kaiyan-sheng commented Jan 16, 2019

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.

@kaiyan-sheng kaiyan-sheng added module meta Metricbeat Metricbeat Team:Integrations Label for the Integrations team labels Jan 16, 2019
@kaiyan-sheng kaiyan-sheng self-assigned this Jan 16, 2019
@kaiyan-sheng
Copy link
Contributor Author

One enhancement issue: #11820

@kaiyan-sheng
Copy link
Contributor Author

Adding tags support in AWS module: #12263

@Giaco9
Copy link

Giaco9 commented Jul 31, 2019

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!

@kaiyan-sheng
Copy link
Contributor Author

Hi @Giaco9, thanks for reaching out! If you only want to collect metrics from a specific region, then you can use

- module: aws
  period: 300s
  metricsets:
    - ec2
  regions:
    - us-east-1

If you want to specify both ec2 instances and regions, then you can try cloudwatch metricset:

- module: aws
  period: 300s
  metricsets:
    - cloudwatch
  metrics:
    - namespace: AWS/EC2
      name: ["CPUUtilization", "DiskWriteOps"]
      tags.resource_type_filter: ec2:intance
      dimensions:
        - name: InstanceId
          value: i-0686946e22cf9494a

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.

@kaiyan-sheng
Copy link
Contributor Author

kaiyan-sheng commented Aug 1, 2019

@Giaco9 Filtering by tags/names to decide what are the metrics should be collected (before collecting all metrics) is a feature we don't have right now. Please correct me if I understood wrong 😄 I created a new issue for this #13145, please feel free to comment on it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Metricbeat Metricbeat module Team:Integrations Label for the Integrations team
Projects
None yet
Development

No branches or pull requests

5 participants