Relabel not-ready m3msg queue metrics #3804
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
retry was extremely misleading because they messages weren't being retried. the counter is incremented if the message is scanned at the retryAt time is in the future (i.e not ready to be processed)
Antanukas
pushed a commit
that referenced
this pull request
Oct 5, 2021
retry was extremely misleading because these messages weren't being retried. the counter is incremented if the message is scanned and the retryAt time is in the future (i.e not ready to be processed)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
retry was extremely misleading because these messages weren't being
retried. the counter is incremented if the message is scanned and the
retryAt time is in the future (i.e not ready to be processed)
What this PR does / why we need it:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing and/or backwards incompatible change?:
Does this PR require updating code package or user-facing documentation?: