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" parameter in Cloudwatch metricbeat module #33133

Closed
7 tasks done
girodav opened this issue Sep 20, 2022 · 0 comments · Fixed by #33166
Closed
7 tasks done

[AWS] Add a new "Data Granularity" parameter in Cloudwatch metricbeat module #33133

girodav opened this issue Sep 20, 2022 · 0 comments · Fixed by #33166
Assignees
Labels
aws Enable builds in the CI for aws cloud testing enhancement Team:Cloud-Monitoring Label for the Cloud Monitoring team

Comments

@girodav
Copy link
Contributor

girodav commented Sep 20, 2022

Describe the enhancement:

Introduce a new parameter that customers can use to define the granularity of the datapoints returned by GetMetricData API calls. The parameter should be name "Data Granularity" and to be passed as "Period" for every MetricDataQuery https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_MetricDataQuery.html created

Describe a specific use case for the enhancement or feature:

With the introduction of this new parameter, customer can retrieve high-granular data, but less frequently, leading to cost savings on their AWS bills.

Full context behind this enhancement can be found on this issue elastic/integrations#2913

Scenarios to test before releasing this new feature:

  • "Data Granularity" set lower than "Collection Period" -> Metricbeat should collect data every collection period, with the specified granularity
  • "Data Granularity" set higher than "Collection Period" -> Metricbeat should return a configuration error and fail to start
  • "Data Granularity" equal to "Collection Period" -> Metricbeat should work as it currently does, without the introduction of this feature
  • "Data Granularity" not set -> same as above
  • "Data Granularity" set lower than "Collection Period" -> Metricbeat should report multiple data points per collection period (make sure to check the number of data points is correct)
  • "Data Granularity" equal to "Collection Period" or when "Data Granularity" not set -> Metricbeat should only report one set of data points per collection period
  • Test billing metricset with the granularity parameter different than the metricbeat collection period, and check the event output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws Enable builds in the CI for aws cloud testing enhancement Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant