Error for Lambda Pricing

[hrzbrg]

Hi,

I noticed today that our ICE installation crashes with the following error:

| Error 2018-01-18 08:04:16,965 [com.netflix.ice.processor.BillingFileProcessor] ERROR tag.Operation  - found different units for Lambda-GB-SecondGB

I haven't had the time to investigate further, so I just drop that here.

Regards
hrzbrg

[shaneknapp]

seeing the same thing w/our installation.

[bilalsaleem93]

@hrzbrg and @shaneknapp I recently started to get this error.
Did you find a reason and solution for this.
Thank you

[nfonrose]

Hi Raja, Does you Ice really? Or is it just logging these lines but still working? This message appears because there is an inconsistency between "Measurement Units" for different billing lines for the AWS Lambda service. Nicolas PS : You might want to try Jim Roth's fork of Ice (it is very up-to-date). https://github.com/jimroth/ice

…

-- Nicolas Fonrose | Teevity | Founder +33.6.61.35.43.31 https://teevity.com - Cloud Costs Analytics for AWS, GCP and Azure powered by NetflixOSS Ice twitter - @nfonrose / @Teevity

On Fri, Jan 31, 2020 at 8:07 AM Raja Bilal Saleem ***@***.***> wrote: @hrzbrg <https://github.com/hrzbrg> and @shaneknapp <https://github.com/shaneknapp> I recently started to get this error. Did you find a reason and solution for this. Thank you — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#283?email_source=notifications&email_token=AAAJJJNTUHYQJOLSGHL77V3RAPE4HA5CNFSM4EMKFRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNW2YA#issuecomment-580611424>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJJJNZNV4NUQHFLLV2ZW3RAPE4HANCNFSM4EMKFRAQ> .

[bilalsaleem93]

Hi Nicolas, I have been using Ice for past 4 years and it has been working like a charm. Recently, i start to get the failure logs and Ice stopped working after that time. Basically, this start once, I purchased the savings plan from AWS which is introduced recently. Any hints on how this can be fixed? Moreover, i am using Jim Roth's fork of Ice as well but it also stopped working in Nov,2019. It would be helpful to know if you or anyone else also started to face this issue in Ice with the purchase of savings plan. And if they get to solve the problem. Regards, Raja Bilal Saleem. On Fri, Jan 31, 2020 at 7:10 PM Nicolas Fonrose <[email protected]> wrote:

…

Hi Raja, Does you Ice really? Or is it just logging these lines but still working? This message appears because there is an inconsistency between "Measurement Units" for different billing lines for the AWS Lambda service. Nicolas PS : You might want to try Jim Roth's fork of Ice (it is very up-to-date). https://github.com/jimroth/ice -- Nicolas Fonrose | Teevity | Founder +33.6.61.35.43.31 https://teevity.com - Cloud Costs Analytics for AWS, GCP and Azure powered by NetflixOSS Ice twitter - @nfonrose / @Teevity On Fri, Jan 31, 2020 at 8:07 AM Raja Bilal Saleem < ***@***.***> wrote: > @hrzbrg <https://github.com/hrzbrg> and @shaneknapp > <https://github.com/shaneknapp> I recently started to get this error. > Did you find a reason and solution for this. > Thank you > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > < #283?email_source=notifications&email_token=AAAJJJNTUHYQJOLSGHL77V3RAPE4HA5CNFSM4EMKFRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNW2YA#issuecomment-580611424 >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAAJJJNZNV4NUQHFLLV2ZW3RAPE4HANCNFSM4EMKFRAQ > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#283?email_source=notifications&email_token=AEHIQA63BXT525X46LVVV6LRAPMGDA5CNFSM4EMKFRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKN3MAA#issuecomment-580630016>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEHIQA3AOETR73R2LKDRLITRAPMGDANCNFSM4EMKFRAQ> .

[nfonrose]

Hi Raja, Thanks for the details. ERROR tag.Operation - found different units for Lambda-GB-SecondGB Your purchase of SavingsPlan (SP) and the associated new billing lines that have appeared in your billing files as a result, and the above error message are unrelated. Can you get in touch with us at [email protected] so that we can better help? We will post the outcome here so that the community can benefit from the solution. Nicolas

…

-- Nicolas Fonrose | Teevity | Founder +33.6.61.35.43.31 https://teevity.com - Cloud Costs Analytics for AWS, GCP and Azure powered by NetflixOSS Ice twitter - @nfonrose / @Teevity On Sun, Feb 2, 2020 at 1:56 AM Raja Bilal Saleem <[email protected]> wrote:

Hi Nicolas, I have been using Ice for past 4 years and it has been working like a charm. Recently, i start to get the failure logs and Ice stopped working after that time. Basically, this start once, I purchased the savings plan from AWS which is introduced recently. Any hints on how this can be fixed? Moreover, i am using Jim Roth's fork of Ice as well but it also stopped working in Nov,2019. It would be helpful to know if you or anyone else also started to face this issue in Ice with the purchase of savings plan. And if they get to solve the problem. Regards, Raja Bilal Saleem. On Fri, Jan 31, 2020 at 7:10 PM Nicolas Fonrose ***@***.***> wrote: > Hi Raja, > > Does you Ice really? Or is it just logging these lines but still working? > This message appears because there is an inconsistency between "Measurement > Units" for different billing lines for the AWS Lambda service. > > Nicolas > > PS : You might want to try Jim Roth's fork of Ice (it is very up-to-date). > https://github.com/jimroth/ice > > > -- > Nicolas Fonrose | Teevity | Founder > +33.6.61.35.43.31 > https://teevity.com - Cloud Costs Analytics for AWS, GCP and Azure powered > by NetflixOSS Ice > twitter - @nfonrose / @Teevity > > > > On Fri, Jan 31, 2020 at 8:07 AM Raja Bilal Saleem < > ***@***.***> > wrote: > > > @hrzbrg <https://github.com/hrzbrg> and @shaneknapp > > <https://github.com/shaneknapp> I recently started to get this error. > > Did you find a reason and solution for this. > > Thank you > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > < > #283?email_source=notifications&email_token=AAAJJJNTUHYQJOLSGHL77V3RAPE4HA5CNFSM4EMKFRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNW2YA#issuecomment-580611424 > >, > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AAAJJJNZNV4NUQHFLLV2ZW3RAPE4HANCNFSM4EMKFRAQ > > > > . > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #283?email_source=notifications&email_token=AEHIQA63BXT525X46LVVV6LRAPMGDA5CNFSM4EMKFRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKN3MAA#issuecomment-580630016 >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AEHIQA3AOETR73R2LKDRLITRAPMGDANCNFSM4EMKFRAQ > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#283?email_source=notifications&email_token=AAAJJJKLBKFHRXUUETETBMTRAYK5PA5CNFSM4EMKFRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRKTRQ#issuecomment-581085638>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJJJP6YX734Y3QUVMHHK3RAYK5PANCNFSM4EMKFRAQ> .