Karen Asmarian

I don't have any good progress on this issue, unfortunately. The thread that is used during write of `LastHttpContent` doesn't have the baggage items in its context. I assume this...

@whiskeysierra @msdousti @ChristianLohmann what do you all think? I'm wondering why this wasn't the case all along for Logbook interceptors, as failures to log request/response shouldn't result in the whole...

@marcindabrowski now interceptors as well as DefaultLogbook will have the logic inside try-catch blocks, which should prevent failures of request/response processing and will only result in not logging them. Thanks...

Looks like a nice addition to logbook. @itineric would you be interested in contributing to the library to add the necessary changes?

It is possible to write your own implementation of [HttpLogFormatter](https://github.com/zalando/logbook/blob/main/logbook-api/src/main/java/org/zalando/logbook/HttpLogFormatter.java) and have colors defined there. If you're using Spring, just having a bean of type `HttpLogFormatter` will be sufficient.

Is it related to https://github.com/zalando/logbook/issues/1710?

Logbook doesn't add/modify headers on its own. I assume the library that you're using for tracing is modifying the trace header either after the logbook was invoked on the requesting...