-
Notifications
You must be signed in to change notification settings - Fork 435
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 per second billing not supported #274
Comments
Hello Gerrit, Thanks for reporting this. Could you screenshot two more screens from your environment please ? In both you would have the same time period, in hourly aggregate, and would filter to only keep ec2_instances, with groupBy "usage type" (aka instance type in this case) ?
You can obvisouly blur the figures on your screenshots. Thanks, Nicolas |
Thanks. Can you do the same and keep only m4.large instances ? (I'm sorry to have to ask this, but we don't have "Ice OSS" instances running so we can't quickly reproduce your issue). |
I can confirm this, happening for us as well. |
Ok. We are going to investigate quickly.
Nicolas
Le jeu. 2 nov. 2017 à 13:34, Amanpreet Singh <[email protected]> a
écrit :
I can confirm this, happening for us as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#274 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACUpYxNLOfn7p-ZKJNYpS4VeLC4esmcks5syba-gaJpZM4QMQfk>
.
--
--
Nicolas Fonrose | Teevity | Founder
+33.6.61.35.43.31
https://teevity.com - Cloud Costs Analytics built on NetflixOSS
twitter - @nfonrose / @Teevity
|
FYI: for some reason the reports are getting processed correctly again now |
It seems to be working for us too. |
Thanks for the feedback.
…--
Nicolas Fonrose | Teevity | Founder
+33.6.61.35.43.31
https://teevity.com - Cloud Costs Analytics built on NetflixOSS
twitter - @nfonrose / @Teevity
On Mon, Nov 6, 2017 at 9:46 AM, Gerrit Germis ***@***.***> wrote:
FYI: for some reason the reports are getting processed correctly again now
Don't known if you guys contacted AWS about the csv files or if this is
just a temporary fix they did, but for now all seems to be back in order
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACUpdBjqdYJM9cq35epjeHEfsfxnt4_ks5szsdigaJpZM4QMQfk>
.
|
AWS introduced per second billing which became effective on october 2nd:
https://aws.amazon.com/blogs/aws/new-per-second-billing-for-ec2-instances-and-ebs-volumes/
The current version of ice does not seem to handle the detailed report billing information correctly for ec2_instances and ebs
See attached graph
The cost for both ec2_instances and ebs are not taken into account anymore
The text was updated successfully, but these errors were encountered: