There is a PR <https://github.com/apache/logging-log4j2/pull/644> for this issue, shall we bring this to a conclusion?
I am in favor of this PR if the following changes were implemented: - limit is read from a property - limit is documented - stay quiet (i.e., not StatusLogger exception logging) if the limit has been exceeded My rationale for the "stay quiet" feature is that, if the runtime exhibits a behavior not anticipated by the configuration, rather than nuking the StatusLogger, simply practice the configuration: recurse no more. This said, I am struggling to not get drawn into Carter's following remark: *"I'm not sure I entirely understand what we're protecting against – I'd consider any recursion beyond what the configuration author expects to be an incredibly serious problem"*. Note that I am not strongly opinionated about the feature per se. I just want to bring the discussion to a conclusion. If we decide to reject the PR (preferably, with a good argument), that is fine by me too.
