Hi <@UDVMV4NBU>, just a quick question to verify s...

# micronaut

[Paul Stott]

Hi @Graeme, just a quick question to verify some understanding and possibly raise an issue if necessary… We are using the CircuitBreaker annotation on a micronaut @Client and we are observing that the original exception that caused the circuit to open is being logged as an error for all subsequent invocations (Line 205 of RecoveryInterceptor.java) until the circuit closes again. I can see the reasoning behind this, but the side effect is that our logs get thrashed during high load. Could you verify that our understanding is correct and do you think an option to suppress logging the exception whilst the circuit is open would be a possibility ?