I think you can set some Logger options at runtime, e.g.
Logger.configure(level: :debug)
# Or on a specific module:
Logger.put_module_level(SomeModule, :debug)
I’ve done this in cases like the one you mentioned where you just need to see what’s going on… something like firing a “tracer round”, e.g. triggered by a query parameter or request header.
However, there are caveats to this, e.g. the logger settings applied only affect the current process, so if your response dispatches execution to other processes (e.g. a database lookup), you may not be enabling the visibility that you think you are.
There are some other subtle and complex caveats (and I’ll defer to the expertise of others here). For instance, if you have configured your app in such a way that logging macros cause the logging statements to be removed from the compiled artifact entirely (e.g. via :compile_time_purge_matching), then no amount of run-time tweaks will make any difference because the statements are no longer present.
