We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Addition of retry-count in the event headers to identify the retry count of an event
It will be helpful to see how many times an event is being retried , hence addition of a new field in the datum can help When would you use this?
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
This can only be an approximate and need not be monotonically increasing. If the pod crashes in between, the counter will be reset.
Sorry, something went wrong.
Yes, will be same as our retry strategy.
No branches or pull requests
Summary
Addition of retry-count in the event headers to identify the retry count of an event
Use Cases
It will be helpful to see how many times an event is being retried , hence addition of a new field in the datum can help
When would you use this?
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: