PowerBI ADX - Rate Optimization Report Issues

[MS-mikeo]

🐛 Problem

I am working on a customer deployment (MCA) where we redeployed the latest version of FinOps Hub with ADX, reconfigured all exports (FOCUS, price sheet, reservation details, reservation transactions) at the Billing Profile level and there are still certain RIs showing as $0 savings in the Commitments tab of the Rate Optimization PowerBI report.

📷 Screenshots

No RIs showing savings before changing the filter settings.

ℹ️ Additional context

Does the order of ingesting the Price Sheet matter? Just wondering if there is any impact to doing it before or after the Focus data set when initially setting up the Hub.

🙋‍♀️ Ask for the community

1. Please vote this issue up (👍) to prioritize it.

[MS-mikeo]

I am currently seeing this on another customer deployment as well.

[GHogbin]

Have this issue on multiple MCA customers too, they have re-ingested the PriceSheet and then folllowed with Costs re-ingestion. I have also taken data and ingested into a new FinOps v12 deployment and get the same result.

The Contracted cost for the RI's is incorrect too

[josesarsa]

Even downgrading to older versions does not help at all. The same outcome. It seems to be something related with the data

[japyjaap]

Having the same issue on both a MCA and a EA client. Moved from storage to Data Explorer version. Reporting worked fine in the storage. We did a whole new deployment by the way. I suppose it has something to do with Data Explorer.

Since I'm aware of the fact that you need to export prices first. I performed the exports in the right sequence. Apparently there is another problem than just not having the price information before the join.

[japyjaap]

I dug into the template ADX report and the issue is there as well. When I look at the numbers in the summary all my reservations savings are shown as expected. I've added the list cost and this is also showing expected figures.

However, when I dive into the Rate Optimization tab the Reservation savings are not shown because the list price is shown as '0'. The Savings plans savings are shown correctly. Since the list cost is missing for the reservation, the list cost shown in the savings summary is incorrect (obviously it is a different number than the list cost on the summary page when looking for instance for the last and current month).

So my conclusion is that somewhere the join to connect the list price of reservations goes wrong. The list cost are available because the data in summary is correct.

With this knowledge I've looked into the PowerBI Savings report again. When I look at the same data (list cost, contract costs, biled cost, effective cost x_NegotiatedDiscountSavings and x_commitmentdiscountsavings) and deselect Principal from the x_AmortizationType Column, I see the following happing:

• listcost are shown with commitments with commitmentdiscoutnttype "reservation"
• billed cost are '0' for both, I suppose this is correct because I'm only looking at effective (amortised) cost
• negotiated discount (difference between list cost and contracted cost) is the discount percentage based on our MACC - this percentage is correct
• the x_commitmentdiscountsaving amount is 0. Which obviously isn't as expected. The effective cost is equal to the list price.

When I then select the principal field in the x_AmortizationType Column as well the following occurs:

• billed cost are shown now which makes sense since we're looking at both the effective (amortised) as billed (actual cost)
• the x_commitmentdiscountsaving for Discounttype 'Savingsplan' is the difference between Contracted cost and effective cost, which makes sense. The effective savings rate however is way lower than the actual percentage those numbers.
• there is also a column x_commitmentdicountsavingsrunningtotal which does reflect the expected saving looking at the effective cost. When I add the negotiated discount amount to this column and divide it by the difference between list cost and effective cost (= x_commitmentdiscountsaving), I end up with the correct ESR. I don't really understand the setup.
• the x_commitmentdiscountsaving for Discounttype 'Reservation 'amount is the same as the billed cost amount. Which obviously isn't as expected. The commitmentdiscountsavingrunningtotal is '0'
• the sum of effective cost and billed cost is exactly the list cost for acounttype 'Reservation'
• the endtotal of X_commitmentdiscountsavingsrunningtotal is exactly the dame commitmentdiscountsavings, however the line items don't add up to that amount
• I've also confirmed with the data in the Azure portal that Effective cost an BilledCost are correct

Ultimately my conclusion is that the calculation of x_CommitmentDiscountSaving for the discount type 'Reservation' is wrong. And since this is used for other calculations with reservations other figures are incorrect as well (the show list price, ESR). I've looked at the data for hours now and I don't really understand the way the savings are calculated, would be nice to have some documentation on how this is structured.

With another client I still have 0.11 running. The savings report is fine in 0.11. I guess the X_commitmentdiscountsavingsrunningtotal is introduced in 0.12. Might this have something to do with failing of the reservation savings?

@MSBrett I suppose this is not only a PowerBI problem, but a broader issue.