Hmm..do you mean system wide value? We can still have the wrap around frequency configurable, but unless we want it customized per log line (I’m not sure if this is really needed?), a system wide config may still be possible to configure, no?
> On Oct 19, 2020, at 7:04 AM, Alan Carroll > <solidwallofc...@verizonmedia.com.invalid> wrote: > > My concern at this point is the lack of configurability of the throttle > time. The underlying implementation supports it but by wrapping it directly > in the logging call, only the default value can be used.
