Skip to content

Bug: Log level not picked up #130

Open
@chrisforrette

Description

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!

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions