When Netty's ResourceLeakDetector prints a report about leaked buffers, there is currently no way to match those to log messages for the request where the ByteBuf was created. We can use ByteBuf#touch with the log prefix for the request (based on the channel id) when debug logging is enabled, similar to what Reactor Netty does.