-
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
Add AWS Cost and Usage reports to Metricbeat #20103
Comments
Pinging @elastic/integrations-platforms (Team:Platforms) |
Thank you @stevewritescode for creating this issue. Yes, |
Hi @stevewritescode , I started a draft PR on adding cost explorer billing metrics for AWS. Please feel free to comment on the PR. Event output examples are here: https://github.com/elastic/beats/pull/20527/files?file-filters%5B%5D=.json |
Wanted to follow-up on this and let you know that I built 7.x branch and setup aws billing with the example steps in the PR, and I was able to see daily unblended costs by service, which is exactly what I wanted! I double checked with the AWS cost explorer console to make sure the numbers matched. Works great! |
😬 @stevewritescode That's awesome. Thank you for testing this!!! |
Describe the enhancement:
Create a Metricbeat module to import AWS cost and usage data, e.g. detailed billing information.
Describe a specific use case for the enhancement or feature:
The current AWS Billing Metricbeat module pulls in billing data from AWS. From what I can tell, the only data that's available through this module is EstimatedCharges since that's the only metric sent through AWS CloudWatch under
AWS/Billing
- I'd like to have rich billing information so that I can monitor AWS account usage in Elastic without needed to go log in to the AWS console cost explorer. Of course, once it's in Elastic then I can leverage all the visualization, ML, and alerting capabilities :)I seen a few open-source projects that are built around this concept but none that use metricbeat. The AWS Go SDK supports costexplorer functions, so it would be natural to integrate with metricbeat the same way that the AWS Cloudwatch module works.
The text was updated successfully, but these errors were encountered: