|
|
@@ -85,6 +85,16 @@
|
|
|
when it happens you will have the full information, including debug and info
|
|
|
records. This provides you with all the information you need, but only when
|
|
|
you need it.
|
|
|
+- _DeduplicationHandler_: Useful if you are sending notifications or emails
|
|
|
+ when critical errors occur. It takes a logger as parameter and will
|
|
|
+ accumulate log records of all levels until the end of the request (or
|
|
|
+ `flush()` is called). At that point it delivers all records to the handler
|
|
|
+ it wraps, but only if the records are unique over a given time period
|
|
|
+ (60seconds by default). If the records are duplicates they are simply
|
|
|
+ discarded. The main use of this is in case of critical failure like if your
|
|
|
+ database is unreachable for example all your requests will fail and that
|
|
|
+ can result in a lot of notifications being sent. Adding this handler reduces
|
|
|
+ the amount of notifications to a manageable level.
|
|
|
- _WhatFailureGroupHandler_: This handler extends the _GroupHandler_ ignoring
|
|
|
exceptions raised by each child handler. This allows you to ignore issues
|
|
|
where a remote tcp connection may have died but you do not want your entire
|