Skip to content

Add meta-data to DLQ #5310

Closed
Closed

Description

@rocketraman

Is your feature request related to a problem? Please describe.
The automatic DLQ is a nice feature, but its lacking any ability to add meta-data to the entry in the DLQ. For example, setting a property like "causalException" with an exception message and stack trace is very useful when looking at the entries in the DLQ and deciding how to handle them.

Describe the solution you'd like
One possible solution may be to allow passing additional properties to the negativeAcknowledge method. When an entry is created in the DLQ, the additional props provided would be added to the DLQ message properties.

Alternatives
Manual DLQ handling. Use Pulsar's redelivery count to manually produce to a DLQ topic, along with the necessary meta-data. This implies that the redelivery count is populated in the Message regardless of the presence of a DeadLetterPolicy. I haven't checked whether that is the case or not.

Activity

  1. added
    type/featureThe PR added a new feature or issue requested a new feature
    on Oct 3, 2019
  2. sijie commented on Oct 27, 2019

    @sijie
    Member

    @codelipenghui @congbobo184 this is a good feature to add to DLQ

  3. codelipenghui commented on Nov 5, 2019

    @codelipenghui
    Contributor

    Sorry for the late response, i will take a look soon.

  4. jefferyshivers-toast commented on Mar 16, 2021

    @jefferyshivers-toast

    Has there been any movement on this? This is an example of a similar feature in Azure Service Bus: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dead-letter-queues#moving-messages-to-the-dlq.

  5. locked and limited conversation to collaborators on Dec 9, 2022
  6. converted this issue into a discussion #18840 on Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions