Skip to content
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

Glances Containers API Memory usage does not match Primary Output #3105

Open
gflip220 opened this issue Feb 14, 2025 · 0 comments
Open

Glances Containers API Memory usage does not match Primary Output #3105

gflip220 opened this issue Feb 14, 2025 · 0 comments

Comments

@gflip220
Copy link

Moving this to an issue as I have been able to recreate the bug on a separate environment.

Discussed in #3099

Originally posted by gflip220 February 5, 2025
While working to setup integration between Glances and GetHomepage.dev, I have noticed an issue where the Glances API seems to report incorrect docker container memory usage, while the Glances primary output reports correct usage. Screenshot below showing Docker Stats matching with Glances output, while Glances API reports a massively higher number, 3GB in this example. Other containers captured in this example are also have similar dependencies.

I am running this on Ubuntu 24.04 with the ubuntu-latest-full version of Glances on Docker.
Glances 4.3.0.7 with psutil 6.1.1

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants