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

Occasional MASSIVE cpu metrics?? #112

Closed
MaxFlanders opened this issue Jul 13, 2016 · 5 comments
Closed

Occasional MASSIVE cpu metrics?? #112

MaxFlanders opened this issue Jul 13, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@MaxFlanders
Copy link

Occasionally dockerbeat is throwing a log with cpu.totalUsage off of the charts. Like unrealistically high, representing more cpu than our memory has (knowing you get 100% per cpu).

Example:

image

Have you guys seen this before or know what could cause something like this??

Thanks!

@tsg
Copy link

tsg commented Jul 13, 2016

This looks quite similar to something we had in Topbeat, see this PR that fixes it. The usage of unsigned integers caused small negative values to be transformed in huge positive values.

Looking at the dockerbeat code, the same might be happening here.

@marminthibaut marminthibaut added this to the 1.0.0 milestone Jul 15, 2016
@MaxFlanders
Copy link
Author

Any update on this issue?? This is literally the only thing preventing us from utilizing this tool in production unfortunately :(

@marminthibaut
Copy link
Member

I'll be on it on Thursday 🐎

@marminthibaut
Copy link
Member

marminthibaut commented Aug 5, 2016

@326TimesBetter I just opened the PR #116 -> Can you check if this version of dockerbeat resolve your issue? If you don't want to compile dockerbeat yourselft, here is a compiled version for linux x86_64 architecture.

Thanks!
dockerbeat.zip

@marminthibaut
Copy link
Member

marminthibaut commented Aug 8, 2016

@326TimesBetter ??

I wouldlike to release 😀

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

No branches or pull requests

3 participants