Filip Skirtun

I just verified that rolling over to previously working image (sha256:4ad0c2f56538c383f1b3a90ccc756fcf937f0a436fafb88a23b9a780164f7be9) gets the metric gathering process working again, thus I think that it is not a local issue.

Thank you for a confirmation of that :) Is it expected that the aforementioned version will log no metrics to Prometheus and should we stick to the estimator-less version for...

Hello sunya-ch and thanks for giving this some attention! - Pod's metrics are correctly reported with expected pods from expected nodes - I can see pod_energy_stat and other expected metrics...

Good to hear then : ) Going back to issue topic, the estimator.sock issue has been well explained (as WIP & expected) and I think we can close this to...

Not going to commit right now since I don't know whether there will be time to address this, but will look into it. Quick question: is there a direct replacement...

So it seems that "pod_energy_total" & "pod_energy_current" is almost same as "pod__energy_in_pkg_millijoule" and these could theoretically be used as a replacement, correct?

Taking a look at commit de3584a9c3a754b17762b08e9494950f7c3b14d3 it seem to historically be calculated as core+dram.

it might have sense to fetch the last "total" metric from of a suitable node (if present) directly from Prometheus when starting kepler's pod, but as mentioned - the numbers...

@rootfs I have also seen this happening on Ice Lake CPUs (RHEL8.6-derivative kernel 4.18) for recent commits, can this be related to #120, #150 and #156? I have lost track...

I have seen one similar bug from a few months before, #96. @rootfs, how can we check if this is an instance of that? The part about "working for just...