Skip to content
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

Open
ggermis opened this issue Oct 31, 2017 · 9 comments
Open

AWS per second billing not supported #274

ggermis opened this issue Oct 31, 2017 · 9 comments

Comments

@ggermis
Copy link

ggermis commented Oct 31, 2017

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
screen shot 2017-10-31 at 07 09 41

The cost for both ec2_instances and ebs are not taken into account anymore

@nfonrose
Copy link
Member

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) ?

  • One screenshot with "Cost data"
  • The same but with "Usage data"

You can obvisouly blur the figures on your screenshots.

Thanks,

Nicolas

@ggermis
Copy link
Author

ggermis commented Oct 31, 2017

Hi Nicolas

Here are the extra requested screenshots

1

2

@nfonrose
Copy link
Member

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).

@ggermis
Copy link
Author

ggermis commented Oct 31, 2017

as requested

1

2

@ApsOps
Copy link

ApsOps commented Nov 2, 2017

I can confirm this, happening for us as well.

@nfonrose
Copy link
Member

nfonrose commented Nov 2, 2017 via email

@ggermis
Copy link
Author

ggermis commented Nov 6, 2017

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

@ApsOps
Copy link

ApsOps commented Nov 6, 2017

It seems to be working for us too.

@nfonrose
Copy link
Member

nfonrose commented Nov 6, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants