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

[Metricbeat] Adding AWS EBS Metricset #11699

Closed
8 tasks
kaiyan-sheng opened this issue Apr 8, 2019 · 0 comments · Fixed by #13167
Closed
8 tasks

[Metricbeat] Adding AWS EBS Metricset #11699

kaiyan-sheng opened this issue Apr 8, 2019 · 0 comments · Fixed by #13167
Assignees
Labels
module Team:Integrations Label for the Integrations team test-plan Add this PR to be manual test plan v7.4.0

Comments

@kaiyan-sheng
Copy link
Contributor

Amazon Elastic Block Store (Amazon EBS) sends data points to CloudWatch for several metrics. Data is only reported to CloudWatch when the volume is attached to an instance.
A list of AWS EBS metrics from Cloudwatch: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-volume-status.html

Metricbeat Module / Dataset release checklist

This checklist is intended for Devs which create or update a module to make sure modules are consistent.

Modules

For a metricset to go GA, the following criterias should be met:

  • Integration tests exist
  • System tests exist
  • Automated checks that all fields are documented
  • Documentation
  • Fields follow ECS and naming conventions
  • Dashboards exists (if applicable)

Metricbeat module

  • Example data.json exists and an automated way to generate it exists (go test -data)
  • Test environment in Docker exist for integration tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module Team:Integrations Label for the Integrations team test-plan Add this PR to be manual test plan v7.4.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants