As indicated in Issue #34, sometimes you can get unexpected behavior when a metlog client that is stored in the CLIENT_HOLDER is replaced but one or more metlog decorators had cached the original, no-longer-in-use client. It might be useful to have a client cache invalidation callback setup, where the CLIENT_HOLDER would be able to invalidate the decorators' cached clients as needed. Please see the Issue #34 discussion for a bit more detail.
As indicated in Issue #34, sometimes you can get unexpected behavior when a metlog client that is stored in the CLIENT_HOLDER is replaced but one or more metlog decorators had cached the original, no-longer-in-use client. It might be useful to have a client cache invalidation callback setup, where the CLIENT_HOLDER would be able to invalidate the decorators' cached clients as needed. Please see the Issue #34 discussion for a bit more detail.