-
Notifications
You must be signed in to change notification settings - Fork 579
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 columns for "Baseline bandwidth" and "Burst bandwidth" #617
Comments
Nice. I think we are trying to get away from scraping but I’ll check the cost APIs and see if I can pull it from there. |
This is actually useful a lot for Elasticache, there is a Cloudwatch metric that shows "Network Bandwidth In Allowance Exceeded" and "Network Bandwidth Out Allowance Exceeded". The burst bandwidth is useful, but ultimately is just that - burst balance. Baseline bandwdith is far more useful for sustained high bandwidth compute (e.g. Elasticache). AWS can drop packets in this situation, and there is no Cloudwatch Metric to show 'dropped packets'. We use the Therefore adding these metrics to this tool would make it even more amazing. For bonus points, making it a column, so we can compare easily. |
Is it possible to extract data from
|
"Up to X Gbps" is not very useful, thankfully AWS provides the actual baseline and burst network bandwidths. Here are the links for general purpose, compute optimized, memory optimized, storage optimized and accelerated computing.
The text was updated successfully, but these errors were encountered: