Can SerializationFailureHandler be used to implement a Global DLQ strategy?

[tryasta]

We are trying to implement a policy for serialization failures that writes to a global dead letter queue.

We have observed that typically serialization errors/failures occur when the message size is larger than what kafka topics allow.
When that happens we would like to implement a strategy in which these messages are sent to a global DLQ (different from the service DLQ meant for deserialization errors) and we considered SerializationFailureHandler as a means to handle the error and send to this Global DLQ.

We are finding that while this handler seems fit for fault tolerance strategies, we cannot seem to make it work for our purpose, as we are not able to get the exact record that cause the serialization error.

 class SomeClass implements SerializationFailureHandler;

   @Override
    public byte[] decorateSerialization(Uni<byte[]> serialization, String topic, boolean isKey, String serializer, Object data,
            Headers headers) {
            
            //send the record to the global DLQ topic
    }

Has anyone got experience on this particular subject? Are we going astray by attempting this way of managing serialization failures?

[tryasta]

We finally managed to implement this feature using a SubscriberDecorator as the option above was taking us to a dead-end.