set precision of TCPCollector's metrics to 2 #622
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.
Having precision=0 means that any non frequent metrics will be hidden by
diamond. For example: if interval=60 and a counter incremented once a minute
we have following math done by derivate():
old=1
new=2
derivative_x = 2-1 = 1
derivative_y = 60
result = 1 / 60 = 0.01666666666667
this value is later passed to Metric class which does following if
precision=0:
value = sprintf("%.0f", 0.01666666666667)
as result value becomes 0.