Fixed Docker CPU Percentage's unusual spike when restarting containers #1100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
docker.cpuacct_percentage.*.{user,system}
metrics observed after restarting a docker container appear to be an unusually high spike.This problem is due to the fact that the comparison of two uint values is made by subtraction.
mackerel-agent-plugins/mackerel-plugin-docker/lib/docker.go
Lines 273 to 276 in cbd69a9
This pull request enables to correctly detect that counters have been reset and also set metrics to moderate values in that case.
operational test
before
You can see that
docker.cpuacct_percentage.hoge_2e3173.{user,system}
metrics have huge values after executingdocker restart
command.after