Add metrics for writing or reading size of cursor#11500
Conversation
8c3253e to
445f8f8
Compare
|
@codelipenghui : |
Anonymitaet
left a comment
There was a problem hiding this comment.
Thanks for your contribution. Approved from the language perspective.
|
/pulsarbot run-failure-checks |
68730b2 to
5b6fed9
Compare
a4f991d to
d68e3b5
Compare
michaeljmarshall
left a comment
There was a problem hiding this comment.
I think we might need to remove the single dimension metrics for namespace. See comments for details.
Otherwise, the new metrics look good to me.
d68e3b5 to
105ae9c
Compare
Thanks and I have updated the patch. |
|
@michaeljmarshall Please help review again. |
michaeljmarshall
left a comment
There was a problem hiding this comment.
Looks good. Minor comment about updating a Javadoc.
664539d to
776820a
Compare
### Motivation Currently, there is no visibility about the following activities: - How many bytes are written from a cursor update? - How many bytes are read from loading a cursor? So when the bookkeeper cluster is having heavy traffic, it is hard to tell which topic or namespace contributes most of the traffic. Add metrics at the broker about how many bytes are written and read per cursor/namespace. ### Modifications Add metrics `writeLedgerSize`, `writeLedgerLogicalSize`, `readLedgerSize`. (cherry picked from commit bfae8f6)
### Motivation Currently, there is no visibility about the following activities: - How many bytes are written from a cursor update? - How many bytes are read from loading a cursor? So when the bookkeeper cluster is having heavy traffic, it is hard to tell which topic or namespace contributes most of the traffic. Add metrics at the broker about how many bytes are written and read per cursor/namespace. ### Modifications Add metrics `writeLedgerSize`, `writeLedgerLogicalSize`, `readLedgerSize`.
Motivation
Currently, there is no visibility about the following activities:
So when the bookkeeper cluster is having heavy traffic, it is hard to tell which topic or namespace contributes most of the traffic.
Add metrics at the broker about how many bytes are written and read per cursor/namespace.
Modifications
Add metrics
writeLedgerSize,writeLedgerLogicalSize,readLedgerSize.