starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-25 17:25:57 +03:00

[GH-ISSUE #428] How to change log level? #251

New issue

Closed

opened 2026-03-03 01:27:14 +03:00 by kerem · 13 comments

kerem commented

2026-03-03 01:27:14 +03:00

Owner

Originally created by @0xERR0R on GitHub (Mar 8, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/428

Bitwarden_rs docker container logs each http request with "INFO" message. How can I change the log level to "critical" to avoid these messages. I just want to have only errors in docker log.

I tried to set the environment variable "ROCKET_LOG" to "critical", but the info messages are still there.

Thank you in advance

Originally created by @0xERR0R on GitHub (Mar 8, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/428 Bitwarden_rs docker container logs each http request with "INFO" message. How can I change the log level to "critical" to avoid these messages. I just want to have only errors in docker log. I tried to set the environment variable "ROCKET_LOG" to "critical", but the info messages are still there. Thank you in advance

kerem

2026-03-03 01:27:14 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@mprasil commented on GitHub (Mar 8, 2019):

Hi, you should be able to do this by setting EXTENDED_LOGGING to false.

@mprasil commented on GitHub (Mar 8, 2019): Hi, you should be able to do this by setting `EXTENDED_LOGGING` to false.

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@0xERR0R commented on GitHub (Mar 8, 2019):

I tried it, it looks different (without log level entry), but I still see entries like
GET /api/sync application/json:
=> Matched: GET /api/sync?<data..> (sync)
...

@0xERR0R commented on GitHub (Mar 8, 2019): I tried it, it looks different (without log level entry), but I still see entries like `GET /api/sync application/json:` ` => Matched: GET /api/sync?<data..> (sync)` `...`

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@dani-garcia commented on GitHub (Mar 8, 2019):

You'll need to use both, in this case:

ROCKET_LOG=critical
EXTENDED_LOGGING=false

At the moment the extended logging needs to be disabled because it hardcodes the debug level, in the future we should change that.

@dani-garcia commented on GitHub (Mar 8, 2019): You'll need to use both, in this case: ```sh ROCKET_LOG=critical EXTENDED_LOGGING=false ``` At the moment the extended logging needs to be disabled because it hardcodes the debug level, in the future we should change that.

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@0xERR0R commented on GitHub (Mar 8, 2019):

Thank you, it helped. It works now as expected. This should be documented here: https://github.com/dani-garcia/bitwarden_rs/wiki/Logging

@0xERR0R commented on GitHub (Mar 8, 2019): Thank you, it helped. It works now as expected. This should be documented here: https://github.com/dani-garcia/bitwarden_rs/wiki/Logging

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@mprasil commented on GitHub (Mar 8, 2019):

You can edit the page and add that if you have some time. 😉

@mprasil commented on GitHub (Mar 8, 2019): You can edit the page and add that if you have some time. 😉

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@0xERR0R commented on GitHub (Mar 8, 2019):

I added the "Change the log level" section to the page, please review

@0xERR0R commented on GitHub (Mar 8, 2019): I added the "Change the log level" section to the page, please review

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@mprasil commented on GitHub (Mar 8, 2019):

That is perfect, thanks a lot for this @0xERR0R. I'm going to close this now as it seems the question has been answered and documentation is up to date.

@mprasil commented on GitHub (Mar 8, 2019): That is perfect, thanks a lot for this @0xERR0R. I'm going to close this now as it seems the question has been answered and documentation is up to date.

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@jstirling commented on GitHub (Apr 21, 2019):

I don't think this is a valid solution to the issue. With extended_logging set to false, you no longer receive failed login errors. Which in turn means Fail2Ban won't work.

@jstirling commented on GitHub (Apr 21, 2019): I don't think this is a valid solution to the issue. With extended_logging set to false, you no longer receive failed login errors. Which in turn means Fail2Ban won't work.

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@dani-garcia commented on GitHub (Apr 21, 2019):

This was implemented a couple of weeks ago, check the .env template:
github.com/dani-garcia/bitwarden_rs@253faaf023/.env.template (L46-L50)

@dani-garcia commented on GitHub (Apr 21, 2019): This was implemented a couple of weeks ago, check the .env template: https://github.com/dani-garcia/bitwarden_rs/blob/253faaf02372ec0ce198e2ee480de4a59986d8a6/.env.template#L46-L50

kerem commented

2026-03-03 01:27:15 +03:00

Author

Owner

@jstirling commented on GitHub (Apr 21, 2019):

Seems to have hit the spot. Thanks for the quick reply before my log exploded 😋
Would suggest updating the wiki with that as well.

@jstirling commented on GitHub (Apr 21, 2019): Seems to have hit the spot. Thanks for the quick reply before my log exploded :yum: Would suggest updating the wiki with that as well.

kerem commented

2026-03-03 01:27:16 +03:00

Author

Owner

@emorgoch commented on GitHub (Jul 18, 2019):

So I'm not sure I'm getting this. I've updated my docker (running on unraid) to set ROCKET_LOG=critical, and EXTENDED_LOGGING=false. However, now I'm not getting any logs.

What should be the correct parameters to get just errors (and warnings if needed), as that's what failed login attempts show up as?

@emorgoch commented on GitHub (Jul 18, 2019): So I'm not sure I'm getting this. I've updated my docker (running on unraid) to set ROCKET_LOG=critical, and EXTENDED_LOGGING=false. However, now I'm not getting any logs. What should be the correct parameters to get just errors (and warnings if needed), as that's what failed login attempts show up as?

kerem commented

2026-03-03 01:27:16 +03:00

Author

Owner

@dani-garcia commented on GitHub (Jul 20, 2019):

You can use LOG_LEVEL=warn, but that requires EXTENDED_LOGGING=true. (The available errors are https://docs.rs/log/0.4.7/log/enum.Level.html#variants)

@dani-garcia commented on GitHub (Jul 20, 2019): You can use LOG_LEVEL=warn, but that requires EXTENDED_LOGGING=true. (The available errors are https://docs.rs/log/0.4.7/log/enum.Level.html#variants)

kerem commented

2026-03-03 01:27:16 +03:00

Author

Owner

@emorgoch commented on GitHub (Jul 21, 2019):

Thanks. That seems to be working. May want to updated the Logging documentation, as it says to use ROCKET_LOG instead of LOG_LEVEL.

@emorgoch commented on GitHub (Jul 21, 2019): Thanks. That seems to be working. May want to updated the Logging documentation, as it says to use ROCKET_LOG instead of LOG_LEVEL.