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

Bug: Log level not picked up #130

Open
chrisforrette opened this issue Aug 9, 2023 · 1 comment
Open

Bug: Log level not picked up #130

chrisforrette opened this issue Aug 9, 2023 · 1 comment

Comments

@chrisforrette
Copy link

Hello! I've tried changing the log level for the Verdaccio Helm installation on my cluster to log much less verbosely, but it still seems to log at info level:

kubectl describe configmap -n kube-system npm-verdaccio
...
# log settings
log: {type: stdout, format: pretty, level: error}

and logs still look like:

http <-- 200, user: null(10.10.46.77), req: 'GET /-/ping', bytes: 0/3 
info <-- 10.10.46.77 requested 'GET /-/ping' 
http <-- 200, user: null(10.10.46.77), req: 'GET /-/ping', bytes: 0/0 
info <-- 10.10.46.77 requested 'GET /-/ping' 
http <-- 200, user: null(10.10.46.77), req: 'GET /-/ping', bytes: 0/0 

I've also tried changing level to warn with the same result. My expectation would be that setting level to warn would make it only output warn and error logs, and level = error would be only error logs. Let me know if I appear to be doing something obviously wrong.

Thanks!

@juanpicado
Copy link
Member

juanpicado commented Jan 14, 2024

Works with npm, seems like you are not modifying the right place, maybe wrong config yaml file?

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

2 participants