-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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] Add billing metricset for aws module #14801
Conversation
Out of curiosity - can I easily jump to another region just by clicking the dashboard? |
@mtojek Great question, usually in other aws metricsets, I have a filter for regions so user can jump to different regions by selecting it using the filter. In this case for the estimated billing data, there is no need to add the region filter. Because AWS stores estimate billing charges only in us-east-1 region. For this metricset, it's limited to only query cloudwatch for us-east-1 region for the same reason: https://github.com/elastic/beats/pull/14801/files#diff-e1445680f9751a62f6ede3036549b515R7 |
description: > | ||
`billing` contains the estimated charges for your AWS account in Cloudwatch. | ||
release: beta | ||
fields: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to be empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I believe so. Because this metricset is created using light module with name aws.metrics.EstimatedCharges.max
so it's not gonna be aws.billing.*
.
BC1: Tested manually and it seems that |
Tested with BC4. Works perfect @kaiyan-sheng ! |
Hellow. |
Hi @cxadmin, this billing metricset for now is only getting the estimated charges from CloudWatch. If you want to get multiple billing accounts, you can enable
|
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