https://bugs.openldap.org/show_bug.cgi?id=10267
--- Comment #4 from chris.paul@rexconsulting.net chris.paul@rexconsulting.net --- Yes I mean operations that send a non-success result message, and I also am aware that this would be useless without other information (PeerAddress, AuthzDN).
I'm thinking of DOS situations, where a sudden and continuous burst of load has made performance suffer. Ironically, the amount of logging being done during such a burst of load, causes significantly more load, which brings the server from its knees to on its belly.
I realize that there's no easy fix to this. I realize that if the team is willing to consider solutions, that it won't come soon.
It almost seems that logging should be binary, condensed to as small of a blob as possible for shipping off server for decompression and analysis. Doing log analysis on a running server, especially in a DOS situation, it not feasible.
I'm seeing TB per day of logging in one environment, when on. The "solution" at the moment is to turn off logging, and then use cn=connections,cn=monitor to identify the culprit and reduce the load so that we can turn monitoring back on.