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] Add a new "Data Granularity" advanced parameter for metrics-related integrations #4246

Closed
21 tasks
girodav opened this issue Sep 20, 2022 · 1 comment · Fixed by #4515
Closed
21 tasks
Assignees
Labels
enhancement New feature or request Integration:aws AWS Team:Cloud-Monitoring Label for the Cloud Monitoring team

Comments

@girodav
Copy link
Contributor

girodav commented Sep 20, 2022

Summary

Introduce a new parameter that customers can use to define the granularity of the datapoints returned by GetMetricData API call.

Task

Add data_granularity parameter (metricbeat's PR elastic/beats#33133) to all datastreams relying on the aws/cloudwatch input. This parameter should be shown as “advanced” and not among the main ones (e.g period and region) and should be set by default to be equal to the collection period, if not defined by the customer. The current parameter “period” should be renamed to something like “collection period” to avoid confusion between this and the new granularity-related parameter.

List of datastreams

  • billing
  • cloudwatch_metrics
  • dynamodb
  • ebs
  • ec2_metrics
  • ecs_metrics
  • elb_metrics
  • firewall_metrics
  • kinesis
  • lambda
  • natgateway
  • rds
  • redshift
  • s3_daily_storage
  • s3_request
  • s3_storage_lens
  • sns
  • sqs
  • transitgateway
  • usage
  • vpn
@girodav
Copy link
Contributor Author

girodav commented Oct 25, 2022

elastic/beats#33133 has been merged, so we can start working on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:aws AWS Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant