3 ms·
> And similar for things like DEBUG or TRACE. Usually you reach for those log levels when you want to see extremely verbose information, but... That's not pract
by paulddraper 3y ago
> And similar for things like DEBUG or TRACE. Usually you reach for those log levels when you want to see extremely verbose information, but... That's not practical to enable in production environments, because the volume of logs you produce would be way too high. And if you can't use it in production, you probably shouldn't use it elsewhere! That's what your local debugger is for.
Oh boy, where to start....
1. Staging/pre-prod environments do exist.
2. Debuggers are nice, but they're not everything. I have a loop and want to see the distribution of execution times. Should I really use a debugger, writing down the info from each iteration? Or maybe something a bit more automated (like a log...)?
3. Being able to enable debug logs (for a specific part of the system) is extremely helpful. Datadog makes this super easy to enable finer logging at runtime.*
* More precisely, the application always logs at a fine level. I have Datadog drop debug logs, but at any time I can enable them to help with a problem. https://docs.datadoghq.com/logs/guide/getting-started-lwl/ https://docs.datadoghq.com/logs/guide/getting-started-lwl/