search

microsoft / finops-toolkit

Tools and resources to help you adopt and implement FinOps capabilities that automate and extend the Microsoft Cloud.
https://aka.ms/finops/toolkit
MIT License
305 stars 106 forks source link

Azure Optimization Engine Benefits Usage workbook error in Reservation usage vs. On-Demand prices: 'where' operator: Failed to resolve table or column expression named 'AzureOptimizationPricesheetV1_CL #1129

Open kevinrosal opened 1 day ago

kevinrosal commented 1 day ago

🐛 Problem

After deploying AOE and following the steps on Enabling Azure commitments workbooks as said on this doc: https://microsoft.github.io/finops-toolkit/optimization-engine/setup-options i still receive the error as shown on the screenshots below. This ticket https://github.com/microsoft/finops-toolkit/issues/995 talks about that AzureOptimizationPricesheetV1_CL Log Analytics table to be populated by the Export-PriceSheetToBlobStorage runbook and i was able to run that particular runbook successfully but the Table is still not present on the log analytics workspace.

👣 Repro steps

  1. Go to Benefits Usage Workbook
  2. Click on Open Workbook
  3. Switch to "Reservations" Tab
  4. Error appears on "Reservation usage vs. On-Demand prices" and "Reservation usage vs. Savings Plan prices"

🤔 Expected

To show information about reservations usage vs on-demand prices and reservations usage vs savings plan prices

📷 Screenshots

Giving access to our MCA and Billing profile Image

Workbook Error Image

ℹ️ Additional context

This is an MCA agreement with a tenant that has 17 subscriptions.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.
helderpinto commented 10 hours ago

Thank you for reporting this issue @kevinrosal and for the details shared.

Can you run the Ingest-OptimizationCSVExportsToLogAnalytics runbook by passing pricesheetexports as value for the StorageSinkContainer parameter? If the job succeeds, you just have to wait 10-15 minutes before checking the Benefits Usage workbook again.

This logic runs automatically on a weekly basis and you should not see this error anymore after the first successful run.