-
Notifications
You must be signed in to change notification settings - Fork 37
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
canSkipMetric not called for counters #78
Labels
Comments
@nzroller Any reason this was not added to |
arteam
pushed a commit
to arteam/dropwizard-metrics-influxdb
that referenced
this issue
Oct 20, 2018
This is the same issue as reported in iZettle#78. For some reason, idle counters still get reported. It would be nice if we could not send anything from the client during its idle period.
arteam
pushed a commit
to arteam/dropwizard-metrics-influxdb
that referenced
this issue
Oct 20, 2018
This is the same issue as reported in iZettle#78. For some reason, idle counters still get reported. It would be nice if we could not send anything from the client during its idle period.
arteam
pushed a commit
to arteam/dropwizard-metrics-influxdb
that referenced
this issue
Oct 20, 2018
This is the same issue as reported in iZettle#78. For some reason, idle counters still get reported. It would be nice if we could not send anything from the client during its idle period.
xiaodong-izettle
pushed a commit
that referenced
this issue
Oct 21, 2018
This is the same issue as reported in #78. For some reason, idle counters still get reported. It would be nice if we could not send anything from the client during its idle period.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
canSkipMetric
is currently not called for counters and hence counters are always reported, even if they didn't change. The following patch fixes it. In case it was an oversight and not intentional, I can also submit it again as pull request.The text was updated successfully, but these errors were encountered: