I wanted to follow up to my original post about the cost discrepancy between Container Cost Allocation and similar widgets or reports. I opened a support case, and the engineering team fixed our issue. Furthermore, the Support Engineer indicated the cost between the 2 different methods should be close : " On average, you can expect a 0.65%- 1% approx difference in the k8s cluster cost between the Reports and the Containers page" .
There is a minor difference in costs because of the 2 different paths the data takes between the methodologies.
Just wanted to update in case any one else has an issue similar to ours, they know what to do, and what to expect.
------------------------------
Ray
------------------------------
Original Message:
Sent: 05-23-2022 13:43
From: Ray Littlefield
Subject: Container Cost Allocation Vs. Cluster Name Dimension costs
I have a question for Cloudability users that are using the Kubernetes agent feature to track their container cost. I really like the Kubernetes agent and the 'Container Cost Allocation' section as it displays/exports the containers labels, and that is so useful for our additional chargeback.
I am seeing 2 different prices for any given cluster when looking at the 'Container Cost Allocation' section vs. a report I generate using the dimension 'Cluster Name'. I use the Cost(total) metric, as that that is what the documentation seems to indicate for 'Container Cost Allocation', but I have also tried all the various cost metrics available to me in Reports. I am careful with the date ranges to make sure I am comparing similar dates or ranges. The 'Container Cost Allocation' always comes out much higher than the report using 'Cluster Name' dimension. Are others experiencing similar results ? If so, which cost do you use ?
------------------------------
Ray
------------------------------
#Cloudability