Make sure that the logs won't make a huge failure worse

As described by @rachedbenmustapha in the PR #1 , We need to design some kind of fallback behavior for whenever enough errors occur simultaneously (but slowly) to fill the memory with log entries.

We need to make sure that the log system won't become a worsening factor, and that it won't hog all the memory for itself due to bad design decisions.

The first (and current) version shall be simple, but we need to think about a solution for the long-term.

[GiorgioRegni]

Hey @DavidPineauScality is this ticket still needed? It's 6 months old now so either we need to work on it or we can close it.

It's actually not something we've though about yet. That being said, it's probably one of our lesser worries at the moment.

[rahulreddy]

We could introduce a dumpLevelLimit (configurable and set to some default). This would mean that we would evict entries using FIFO once the number of entries on a request logger reach that limit.