-
Notifications
You must be signed in to change notification settings - Fork 118
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
log spamming #199
Comments
mschneider82
added a commit
to mschneider82/tally
that referenced
this issue
Jan 24, 2023
mschneider82
added a commit
to mschneider82/tally
that referenced
this issue
Jan 24, 2023
Merged
hi, the spammy log message has been removed. this and other fixes will be in the next release |
Ok i made two PR to remove it for both branches. |
brawndou
pushed a commit
that referenced
this issue
Jan 26, 2023
both branches have been updated, will cut a new release once other fixes have also been tested/merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I updated from 3.5.0 to 3.5.2 and now i get my logs spammed with this message:
2023/01/24 10:10:18 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:19 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:20 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:21 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:22 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:23 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:24 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:25 counters: 3, gauges: 34, histograms: 2
2023/01/24 10:10:26 counters: 3, gauges: 34, histograms: 2
It seems that c347bbf introduced a log.Printf line.
The text was updated successfully, but these errors were encountered: