timbre

pez 2024-02-23T09:01:20.701709Z

What are you people using for min-level in different environments? Or, rather, how are you using the log levels, for debugging, observing and so on? Anyone knows of a good resource for reading up on this, I’d love to know.

āœ… 1
2024-02-23T13:24:27.255129Z

a few years ago I realized I was probably logging things at debug level that should be at info, and I found some list that I roughly follow. this one isn't that but it's basically the same levels: https://stackoverflow.com/a/2031209/984393 I use info level in prod, and if I need I set an environment variable, or sometimes recompile, to lower it

šŸ™ 2
pez 2024-02-23T13:28:00.311889Z

Exactly what I was looking for. Thanks! ā¤ļø

šŸ‘ 1
iarenaza 2024-02-24T12:52:57.988289Z

In addition to using the log levels as suggested in the linked StackOverflow entry, what we have in our backends (front-end is another different kettle of fish) is an API endpoint where we can reconfigure timbre log levels on the fly. We usually have a default min-level of INFO globally set (this is configurable via an environment variable, by the way), but we can raise or lower that level on the fly, even per namespace. Thus, by default we don't clutter the logs with DEBUG or TRACE entries (which can amount to a substantial amount of log entries). But when we need to debug some issue we can reconfigure timbre to send those entries to the logs. And chose if we send the entries generated in all namespaces, or just the suspect ones. And once we are done with the debugging, we can switch things back to "low noise" debugging. Thus we use "whichever min-level is suitable for the current environment at this very moment".

šŸ‘ 1