[GH-ISSUE #932] Ability to change log level #144

New issue

Closed

opened 2026-03-03 12:08:41 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 12:08:41 +03:00

Owner

Originally created by @Meemaw on GitHub (Sep 25, 2022).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/932

By default, fake-gcs-server is quite spammy, doing info logging for every request.

Add an ability to change the log level to e.g warn/error

Originally created by @Meemaw on GitHub (Sep 25, 2022). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/932 By default, `fake-gcs-server` is quite spammy, doing info logging for every request. Add an ability to change the log level to e.g `warn/error`

kerem

2026-03-03 12:08:41 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-03 12:08:42 +03:00

Author

Owner

@fsouza commented on GitHub (Sep 25, 2022):

That sounds good to me. We can add a new flag (and eventually an environment variable when we solve #561).

@fsouza commented on GitHub (Sep 25, 2022): That sounds good to me. We can add a new flag (and eventually an environment variable when we solve #561).

kerem commented

2026-03-03 12:08:42 +03:00

Author

Owner

@RachitSharma2001 commented on GitHub (Dec 25, 2022):

@fsouza @Meemaw I was wondering if I could pick this task up. My idea is to include a log-level flag which can be one of two options:

info - log all http requests, warnings, and errors (basically everything)
warn-error - log only warnings and errors
Let me know what you think of this idea and if there is anything else I should change or add.

@RachitSharma2001 commented on GitHub (Dec 25, 2022): @fsouza @Meemaw I was wondering if I could pick this task up. My idea is to include a `log-level` flag which can be one of two options: 1. info - log all http requests, warnings, and errors (basically everything) 2. warn-error - log only warnings and errors Let me know what you think of this idea and if there is anything else I should change or add.

kerem commented

2026-03-03 12:08:42 +03:00

Author

Owner

@fsouza commented on GitHub (Dec 28, 2022):

Hey @RachitSharma2001, I was thinking the flag would be a string and take anything that logrus accept. You could call ParseLevel and if that fails, you report an error to the user indicating invalid log level or something like that.

@fsouza commented on GitHub (Dec 28, 2022): Hey @RachitSharma2001, I was thinking the flag would be a string and take anything that logrus accept. You could call [`ParseLevel`](https://pkg.go.dev/github.com/sirupsen/logrus#ParseLevel) and if that fails, you report an error to the user indicating invalid log level or something like that.

kerem commented

2026-03-03 12:08:42 +03:00

Author

Owner

@RachitSharma2001 commented on GitHub (Dec 28, 2022):

That sounds good! I have made a PR for this. Let me know if there is anything that should be changed or added.

@RachitSharma2001 commented on GitHub (Dec 28, 2022): That sounds good! I have made a PR for this. Let me know if there is anything that should be changed or added.

kerem referenced this issue

2026-03-03 12:29:43 +03:00

[PR #144] [MERGED] Support for bucket creation time #376