Option to reduce or turn off the logs?

[k-mitevski]

This works well but generates too many logs in the output. Is there an option to reduce the log output or completely turn off the logging functionality? Preferably through some flag or something similar.

[ricardomaraschini]

Interesting, what kind of logs are you seeing ? Would you mind sharing ?

[k-mitevski]

The logs look like this and continuously repeat on every check I assume. For three pods, in one hour, the container generated ~230k lines of logs. Which quickly gets expensive. And the more pods you run with oomhero the more logs get proportionally generated.

023/10/26 10:58:28 error reading mem usage for pid 1: error reading memory limit for pid 1: open /sys/fs/cgroup//kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
11:blkio:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
10:freezer:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
9:memory:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
8:hugetlb:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
7:net_cls,net_prio:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
6:cpu,cpuacct:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
5:cpuset:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
4:devices:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
3:pids:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
2:perf_event:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
1:name=systemd:/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a
0::/kubepods/burstable/podc1f64905-7816-4674-a119-c2da28624859/183cff1b5d93697d079ed9b3ccd87be0927e46776cf92dd72849c2816979548a/memory.max: no such file or directory
2023/10/26 10:58:28 memory usage on pid 1446's cgroup: 75%
2023/10/26 10:58:28 memory usage on pid 1474's cgroup: 75%
2023/10/26 10:58:28 memory usage on pid 1475's cgroup: 75%
2023/10/26 10:58:28 memory usage on pid 1476's cgroup: 75%
2023/10/26 10:58:28 memory usage on pid 1477's cgroup: 75%
2023/10/26 10:58:28 memory usage on pid 1478's cgroup: 75%

[k-mitevski]

@ricardomaraschini any update? Do you think this can be fixed somehow