AWS per second billing not supported

[ggermis]

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

[nfonrose]

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]

Hi Nicolas

Here are the extra requested screenshots

[nfonrose]

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]

as requested

[ApsOps]

I can confirm this, happening for us as well.

[nfonrose]

Ok. We are going to investigate quickly.

Nicolas

Le jeu. 2 nov. 2017 à 13:34, Amanpreet Singh notifications@github.com 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 https://github.com/Teevity/ice/issues/274#issuecomment-341407250, 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

[ggermis]

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]

It seems to be working for us too.

[nfonrose]

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 notifications@github.com 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 https://github.com/Teevity/ice/issues/274#issuecomment-342081895, or mute the thread https://github.com/notifications/unsubscribe-auth/AACUpdBjqdYJM9cq35epjeHEfsfxnt4_ks5szsdigaJpZM4QMQfk .