-
Notifications
You must be signed in to change notification settings - Fork 177
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
[BUG] Trace logging is on by default #191
Comments
Hi @jdmarshall , |
It did not for me. I think the conversation elsewhere is that the problem is in the config file, and that the python code is not evaluating environment variables during initialization. |
Yes, I mean config variable, not env variable. You’re right that it should
not be enabled by default
…On Fri, 28 Jan 2022 at 19:17, Jason Marshall ***@***.***> wrote:
It did not for me. I think the conversation elsewhere is that the problem
is in the config file, and that the python code is not evaluating
environment variables during initialization.
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJLTVWTNAJFC4233PXA46LUYLMURANCNFSM5M7PVSYA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Fixed in 1.1.8-6, image will be ready in couple of hours (as automation build it). |
Correction - in 1.1.8-7 |
Please open bug only for Docker component here, if you want to do so for Graphite, please use graphite-web repo
Describe the bug
Nobody needs to see every time a client connects to graphite is opened and closed. This is trace-level information and should be off by default
To Reproduce
Run docker-graphite-statsd, and watch the screen scroll and scroll.
Expected behavior
Error logging to console, and not much else.
Environment (please complete the following information):
Straight out of the box.
Additional context
I'm trying to run this in docker-compose, and I can't read any logs from my apps because graphite is scrolling the window every fifteen seconds:
28/01/2022 01:22:55 :: [listener] MetricLineReceiver connection with 127.0.0.1:46950 established
The text was updated successfully, but these errors were encountered: