Cherry-pick #14801 to 7.x: [Metricbeat] Add billing metricset for aws module#14986
Merged
kaiyan-sheng merged 3 commits intoelastic:7.xfrom Dec 6, 2019
kaiyan-sheng:backport_14801_7.x
Merged
Cherry-pick #14801 to 7.x: [Metricbeat] Add billing metricset for aws module#14986kaiyan-sheng merged 3 commits intoelastic:7.xfrom kaiyan-sheng:backport_14801_7.x
kaiyan-sheng merged 3 commits intoelastic:7.xfrom
kaiyan-sheng:backport_14801_7.x
Conversation
* Add billing metricset for aws module * add dashboard * Update changelog (cherry picked from commit bbb8f1f)
mtojek
approved these changes
Dec 6, 2019
Contributor
mtojek
left a comment
There was a problem hiding this comment.
Preserving no other changes than in the original PR and green status of Travis CI, LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #14801 to 7.x branch. Original message:
AWS stores estimate billing charges in Cloudwatch us-east-1 region for users to see estimate charges for total, or by each service. The values are estimates, not predictions. The estimate approximates the cost of AWS usage to date within the current billing cycle and will increase as users continue to consume resources.
This will be a good use case for alerting so users get alerted when AWS charges are higher than expected
One overview dashboard is built for this metricset:
How to test this
Enable aws module and change aws.yml to:
This takes a while because estimated billing data are sent to Cloudwatch every several hours.
closes #14934