Pranshu Srivastava

`/proc/foo` is associated with the kernel (all files one level under `/proc`). On an fresh docker container, with no userland processes running, `find /proc -maxdepth 2 -name foo` will return...

I believe I assumed the issue to only target `/proc//interrupts`, rather than `/proc/interrupts` too, my bad. We do support the former, but not the latter, as @SuperQ pointed out above....

CI failures don't seem to be stemming from the patch.

Test failure seems to indicate that the filesystem changes dropped significantly since the last commit, I don't see any changes in the reloader that may visibly warrant that though. I'll...

It seems it wasn't moved, but failed to render due to a recent change. ``` Couldn't find target container #hubspotForm-7f3330bd-39c5-4358-b56d-44b90ae62e8e for HubSpot Form 7f3330bd-39c5-4358-b56d-44b90ae62e8e. Not rendering form onto the page...

@simonpasquier Makes sense, I remember doing a similar thing in [`node-exporter`](https://github.com/prometheus/node_exporter/pull/3032/files#diff-7f89527fd186b6ae37f9e36c257f2c48bd15f09596ceaf488d3325d470d4933fR33-R34) a while back (I pointed it to a local directory for convenience (faster changes since the other PR was...

While it's reasonable to put these errors behind a more verbose filter, the reason these happen is because KSM does not know how long to wait for the field population...

ACK, at this point I believe it's best to increase the verbosity level for these errors. I'll send a patch.

This PR is rebased on https://github.com/prometheus-operator/prometheus-operator/pull/6992 to address an issue that crashed the `make generate` target.

This seems fine to work on, since we've had `*_owner` metrics historically.