Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss introducing deadletter mechanisms for transformers #48

Open
clezag opened this issue Dec 4, 2023 · 0 comments
Open

Discuss introducing deadletter mechanisms for transformers #48

clezag opened this issue Dec 4, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@clezag
Copy link
Member

clezag commented Dec 4, 2023

Currently, the documentation requires transformers to simply ack and logs events they are unable to process.

This is probably not a good idea because:

  • Aside from the logs there is no indication that the transformer isn't working correctly
  • Once the issue is solved, we'd have to manually recreate the events that failed from log messages

We should discuss introducing deadletter mechanisms for failed transformer events.
While we're at it, introducing a standardized requeue limit across transformers could be a good idea

@clezag clezag added the enhancement New feature or request label Dec 4, 2023
@clezag clezag added this to the 1st Service on Production milestone Dec 4, 2023
@clezag clezag self-assigned this Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant