alexus
June 21, 2022, 9:32pm
1
Hello World!
I'm following Run Filebeat on Docker | Filebeat Reference [7.17] | Elastic , yet seeing following ERROR in my logs (over and over):
filebeat | 2022-06-21T21:08:17.932Z ERROR metrics/metrics.go:376 error getting cgroup stats: error fetching stats for controller io: error fetching IO stats: error fetching io.pressure for path /sys/fs/cgroup:: open /sys/fs/cgroup/io.pressure: no such file or directory
I'm using latest filebeat-7.17.X version.
btw, I'm getting same message with metricbeat as well
metricbeat | 2022-06-21T21:36:18.052Z ERROR metrics/metrics.go:376 error getting cgroup stats: error fetching stats for controller io: error fetching IO stats: error fetching io.pressure for path /hostfs/sys/fs/cgroup:: open /hostfs/sys/fs/cgroup/io.pressure: no such file or directory
Please advise.
Adriann
(Adrian)
June 21, 2022, 9:44pm
2
I think you should check this
alexus
June 22, 2022, 2:51pm
3
@Adriann , thank you for taking your time to answer my question, i really do appreciate that!
I see that it seems like they already fixed with 8.1.2+, but not in version 7 just yet and it's safe to ignore it as well as it only affects own monitoring.
thank you!
ref:
opened 10:34AM - 23 Dec 20 UTC
closed 04:06PM - 06 Apr 22 UTC
enhancement
discuss
libbeat
help wanted
Team:Elastic-Agent-Data-Plane
Discuss thread: https://discuss.elastic.co/t/metricbeat-k8s-error-getting-group-… status-open-proc-pid-cgroup/255371
Since https://github.com/elastic/beats/pull/21113 monitoring includes cgroup stats. However, those are hardcoded to read from `/proc`. This clashes with use cases where proc is available in a different location and causes the following error to be printed to the logs every 30s:
> ERROR instance/metrics.go:285 error getting group status: open /proc/33861/cgroup: no such file or directory
Metricbeat's system module has a command-line argument, `-system.hostfs`, that allows to specify an alternate path to the root filesystem for these metrics.
We could have a similar flag / configuration option for the monitoring metrics.
opened 10:34AM - 23 Dec 20 UTC
closed 04:06PM - 06 Apr 22 UTC
enhancement
discuss
libbeat
help wanted
Team:Elastic-Agent-Data-Plane
Discuss thread: https://discuss.elastic.co/t/metricbeat-k8s-error-getting-group-… status-open-proc-pid-cgroup/255371
Since https://github.com/elastic/beats/pull/21113 monitoring includes cgroup stats. However, those are hardcoded to read from `/proc`. This clashes with use cases where proc is available in a different location and causes the following error to be printed to the logs every 30s:
> ERROR instance/metrics.go:285 error getting group status: open /proc/33861/cgroup: no such file or directory
Metricbeat's system module has a command-line argument, `-system.hostfs`, that allows to specify an alternate path to the root filesystem for these metrics.
We could have a similar flag / configuration option for the monitoring metrics.
1 Like
system
(system)
Closed
July 20, 2022, 4:51pm
4
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.