| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@tjiuming:Thanks for your contribution. For this PR, do we need to update docs? |
Sorry, something went wrong.
|
Tests to be completed. |
Sorry, something went wrong.
|
/pulsarbot run-failure-checks |
Sorry, something went wrong.
|
/pulsarbot run-failure-checks |
Sorry, something went wrong.
(cherry picked from commit 88b47e5)
|
Hi @tjiuming |
Sorry, something went wrong.
|
Why is something that is NOT A BUG FIX being cherry picked to 2.9 and 2.8? If there is any difficulty this is a risky change that might break an old branch. |
Sorry, something went wrong.
@tjiuming - can you please provide more motivation for this addition? |
Sorry, something went wrong.
|
@michaeljmarshall @dave2wave I have updated the motivation of this PR Currently, we don't have message acknowledgment metrics, which is hard to find the ack-related issues. It's not a new feature, just to improve the observability of the acknowledgment. And I have mentioned this part on the mailing list https://lists.apache.org/thread/wkm1slrg341kbq7m83nms97df28kl4of |
Sorry, something went wrong.
(cherry picked from commit 88b47e5)
| Back | FazBrowse Home | New Git URL |
Motivation
Currently, we have dispatch rate metrics but don't have consumer acknowledgment-related metrics.
Which not easy to troubleshoot issues like some consumers stop acknowledging messages.
Having an ack rate metric would be very useful to determine if our consumers are processing messages properly.
Verifying this change
Documentation
Check the box below or label this PR directly.
Need to update docs?
doc-required
(Your PR needs to update docs and you will update later)
no-need-doc
(Please explain why)
doc
(Your PR contains doc changes)
doc-added
(Docs have been already added)
doc-complete