-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Monitoring] Logs error when we failed to collect information concerning the memory usage. #6426
Comments
We will also need to also return the orignal error here beats/libbeat/metric/system/process/process.go Lines 419 to 424 in 33ff735
|
@ph |
@kvch Correct, it has
They are currently two problems with the error messages:
What do you think, could we improve the log message? This will fix both of the issues. |
@kvch Nevermind saw the PR linked after. more ☕️ |
I'm still getting these errors in logs with metricbeat 6.2.2:
but there is no clue what could be the problem. I'm running official metricbeat docker container and trying to pull stats from host.
Any idea what could be the cause ? |
@Constantin07 I think this deserves a new issue like "Monitoring metrics don't work when containerized". My initial guess is that it cannot find its own metrics in /hostfs/proc because it is pid namespaced and therefore is looking for something like This problem extends from the fact that |
Thanks @andrewkroh. Raised #6620. |
Followup from discuss: https://discuss.elastic.co/t/error-while-getting-memory-usage-error-retrieving-process-stats/120638
We had a report on discuss that some error were raised when collecting information about the memory usage. We currently don't log what was the actual error when calling
Additional information: Metricbeat on Dockerswarm host on AWS using Moby Linux.
Wrapping the original error here
beats/libbeat/cmd/instance/metrics.go
Lines 77 to 81 in 33ff735
The docker tags error is related to a Mapping error
The text was updated successfully, but these errors were encountered: