Thomas Nguyen

@mattray This is something I'd like to return to in the future. But I'm ok closing it for now to keep things tidy.

@liorfranko Thanks for the detailed writeup + screenshots! Looking at this now. Could you provide some additional screenshots on what `node_cpu_hourly_cost` and `node_ram_hourly_cost` look like on an accurate `c5d.18xlarge` versus...

@liorfranko I investigated this a bit further. The following code block is where we are emitting values for `node_cpu_hourly_cost` and `node_ram_hourly_cost`. https://github.com/opencost/opencost/blob/418feea2890ca3a617ba8e33623aae7878b01c76/pkg/costmodel/metrics.go#L534-L558 I suspect that we may be observing outliers...

@liorfranko Still looking into this, but could you provide the following info so we can further troubleshoot: - Logs from the Opencost container which is emitting the incorrect `node_total_hourly_cost` -...

@sachin-rafay Thanks for investigating and proposing a PR here! @liorfranko Does this align with what you're seeing? Is the `node_total_hourly_cost` primarily occurring for spot nodes? For reference, I think this...

@liorfranko Did you see any occurrences of this log line? https://github.com/opencost/opencost/blob/c38dbed76e070a4119186e7d4b7e9999033daecd/pkg/cloud/aws/provider.go#L1309

@deepy I've recently also noticed an environment with cAdvisor returning an IP instead of hostname. This ended up causing issues with OpenCost computing Allocations. @deepy Do you know what versions...

Thanks @janlauber for the PR! I've added some comments to the associated Github issue.

@janlauber So the intended effect here is that if the user specifies `USE_CUSTOM_PROVIDER=true` and are not using a CSV provider, then OpenCost will default to using the pricing found in...

Hey @sossickd! Thanks for the details provided here. Those logs can be safely ignored at this time! You can reduce the log level by setting the `LOG_LEVEL=warn` environment variable. If...