Hey <@U02HQRXU4SD&gt;!Unfortunately, currently not, it's hardcoded at 5MB

ok, thanks

what you can do is to reduce logging levels for some channels that are especially talkative, but beware you're trading observability for space

What is the most frequent event being logged ? Is it error or info level?

let me check

the log fill up with this warning "channel":"CriblMaster","level":"warn","message":"invalid worker connection", the data field in the JSON is huge (about 20-30 MB), this is logged on the leader, and in the src field I have the ip of one of the workers

is there an `info` field in the log? `info.cribl` ?

ah, nvm, there won't be

I will try using some throttling because the bandwidth we have for the specific site is not so big

I think we have a Jira for that issue when large events show up in the leader logs because they aren't supposed to do that

oh ok. I am still using 3.5.2 by the way

ok, throttling changed the connection status from yellow to green