Skip to content
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

nsqd log-level does not work? #1034

Closed
Cryptophobia opened this issue May 16, 2018 · 1 comment
Closed

nsqd log-level does not work? #1034

Cryptophobia opened this issue May 16, 2018 · 1 comment

Comments

@Cryptophobia
Copy link

I provided a config to nsq and built a new container setting the log-level to "fatal". Using the 1.0.0-compat release.

Still seeing a lot of these messages:

[nsqd] 2018/05/16 16:52:03.305057 200 GET /stats?format=json (172.17.0.7:34458) 30.94µs
[nsqd] 2018/05/16 16:52:04.356793 200 GET /stats?format=json (172.17.0.7:34458) 22.734µs
[nsqd] 2018/05/16 16:52:05.831739 200 GET /stats?format=json (172.17.0.7:34458) 26.386µs
[nsqd] 2018/05/16 16:52:06.055195 200 GET /ping (172.17.0.1:50822) 1.208µs
[nsqd] 2018/05/16 16:52:06.317111 200 GET /stats?format=json (172.17.0.7:34458) 45.779µs
[nsqd] 2018/05/16 16:52:07.470238 200 GET /ping (172.17.0.1:50828) 1.259µs
[nsqd] 2018/05/16 16:52:08.048348 200 GET /stats?format=json (172.17.0.7:34458) 42.386µs
[nsqd] 2018/05/16 16:52:08.906895 200 GET /stats?format=json (172.17.0.7:34458) 50.839µs
[nsqd] 2018/05/16 16:52:09.989648 200 GET /stats?format=json (172.17.0.7:34458) 34.546µs
[nsqd] 2018/05/16 16:52:10.432555 200 GET /stats?format=json (172.17.0.7:34458) 23.683µs
[nsqd] 2018/05/16 16:52:11.431870 200 GET /stats?format=json (172.17.0.7:34458) 27.392µs
[nsqd] 2018/05/16 16:52:12.736022 200 GET /stats?format=json (172.17.0.7:34458) 28.311µs
[nsqd] 2018/05/16 16:52:13.872457 200 GET /stats?format=json (172.17.0.7:34458) 20.624µs
[nsqd] 2018/05/16 16:52:14.371104 200 GET /stats?format=json (172.17.0.7:34458) 36.081µs
[nsqd] 2018/05/16 16:52:15.353793 200 GET /stats?format=json (172.17.0.7:34458) 23.521µs
[nsqd] 2018/05/16 16:52:16.056645 200 GET /ping (172.17.0.1:50884) 3.034µs
[nsqd] 2018/05/16 16:52:17.158296 200 GET /stats?format=json (172.17.0.7:34458) 58.252µs
[nsqd] 2018/05/16 16:52:17.451589 200 GET /stats?format=json (172.17.0.7:34458) 28.752µs
[nsqd] 2018/05/16 16:52:17.469686 200 GET /ping (172.17.0.1:50890) 1.293µs
[nsqd] 2018/05/16 16:52:18.417273 200 GET /stats?format=json (172.17.0.7:34458) 37.916µs
[nsqd] 2018/05/16 16:52:19.802161 200 GET /stats?format=json (172.17.0.7:34458) 31.1µs
[nsqd] 2018/05/16 16:52:21.153748 200 GET /stats?format=json (172.17.0.7:34458) 38.991µs
[nsqd] 2018/05/16 16:52:22.181632 200 GET /stats?format=json (172.17.0.7:34458) 26.208µs
[nsqd] 2018/05/16 16:52:22.590354 200 GET /stats?format=json (172.17.0.7:34458) 68.832µs
[nsqd] 2018/05/16 16:52:23.511774 200 GET /stats?format=json (172.17.0.7:34458) 29.205µs
[nsqd] 2018/05/16 16:52:24.831254 200 GET /stats?format=json (172.17.0.7:34458) 74.119µs
[nsqd] 2018/05/16 16:52:25.973757 200 GET /stats?format=json (172.17.0.7:34458) 25.498µs
[nsqd] 2018/05/16 16:52:26.055415 200 GET /ping (172.17.0.1:50946) 1.741µs
[nsqd] 2018/05/16 16:52:26.803016 200 GET /stats?format=json (172.17.0.7:34458) 25.703µs
@Cryptophobia Cryptophobia changed the title nsq log-level does not work? nsqd log-level does not work? May 16, 2018
@Cryptophobia
Copy link
Author

Closing this because #892 means that it was merged in after the latest release. 😢

We need a new release in order to change log-level on nsqd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant