Question regarding Lookup Table

Skip to first unread message

Johannes Grumböck

Sep 4, 2021, 9:28:12 AM9/4/21
to Cloud Carbon Footprint

I'm new to CCF and wanted to take a look into the Lookup Table creation.
What puzzles me is the example Athena query:
The WHERE clause is 'NOT IN ('Usage', 'DiscountedUsage', 'SavingsPlanCoveredUsage')' - why NOT IN?! Shouldn't it be IN?

I asked this, because I looked into our bill CSV files and by filtering with NOT IN I don't get any rows containing vCpus. If I filter with IN then I get a lot of rows including also vCpus values.

Additionally I also see "SavingsPlanNegation" as line_item_line_item_type.

Thanks for your support,

Cloud Carbon Footprint

Sep 9, 2021, 3:56:11 PM9/9/21
to Cloud Carbon Footprint
Hi Johannes,

Thanks for reaching out and pointing out this issue! You are in fact correct. It should be 'IN' rather than 'NOT IN', we made a typo.
We will make that update to the example.
Message has been deleted

Johannes Grumböck

Sep 9, 2021, 4:55:50 PM9/9/21
to Cloud Carbon Footprint
Cool!, thanks for your response!
So far I didn't follow the LookupTable since AWS support is able to backfill our Athena integration with historical data from the last year.
If they wouldn't have this offer I would have tried to scrape our cost & usage reports CSVs from the last months and to come up with some calculations with the Lockuptable,
but honestly I'm glad that I don't need to go this path: I would have struggled which value from CSV to multiply with which value from Lockuptable and second I wouldn't have this nice dashboard!

I additionally created and I'm glad that you're already on it. I'm happy to help on this as much as I can.

Thanks and keep it up!

Cloud Carbon Footprint

Sep 13, 2021, 3:21:27 PM9/13/21
to Cloud Carbon Footprint
Sounds good, Johannes!

We believe we fixed the issue so go ahead and look at it from your end. Feel free to keep making more suggestions to CCF!
Reply all
Reply to author
0 new messages