Hi Lukas,

On Sun, Dec 15, 2019 at 05:23:38PM +0100, Lukas Tribus wrote:
> Currently this debug converter is only enabled when DEBUG_EXPR is
> defined at build time (which is different than other debug build
> options and unclear from the documentation).
> 
> This moves the patch to the default build, so everyone can use it.

I was thinking about repurposing this converter to use the ring buffer
instead, so that it can be used even with live traffic and let one
consult some history from the CLI. We could then have a few info
such as the request ID, and config file+line number where the
converter is present, followed by the pattern.

We could imagine adding one (or multiple) optional arguments to force
the output to another destination (e.g. stdout, stderr, other ring),
and maybe another one for the format or to prepend a prefix. Then most
likely we'd use the ring buffer by default as it's the least impacting
one and the only self-sustaining output. And probably that we could
switch to stderr by default in backports (or make it mandatory to
force the destination).

What do you think ?

Cheers,
Willy

Reply via email to