-
Notifications
You must be signed in to change notification settings - Fork 52
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
client: add new metric instrumentation for reads & appends #317
client: add new metric instrumentation for reads & appends #317
Conversation
Give particular focus to fragment reads, surfacing the number of client-initiated fragment reads and related size metrics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one nit regarding the new counter descriptions.
}, []string{"journal", "codec"}) | ||
readFragmentBytes = promauto.NewCounterVec(prometheus.CounterOpts{ | ||
Name: "gazette_read_fragment_bytes_total", | ||
Help: "Total number of journal fragment bytes read, excluding discarded bytes.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would probably be good for the description here to explicitly state that this is uncompressed, because I could see somebody reading "fragment bytes" as meaning "bytes of compressed fragment data from cloud storage".
}, []string{"journal", "codec"}) | ||
discardFragmentBytes = promauto.NewCounterVec(prometheus.CounterOpts{ | ||
Name: "gazette_discard_fragment_bytes_total", | ||
Help: "Total number of journal fragment bytes discarded while seeking to desired offset.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Reviewable status: 0 of 5 files reviewed, 2 unresolved discussions
broker/client/doc.go, line 91 at r1 (raw file):
Previously, willdonnelly (Will Donnelly) wrote…
It would probably be good for the description here to explicitly state that this is uncompressed, because I could see somebody reading "fragment bytes" as meaning "bytes of compressed fragment data from cloud storage".
Done.
broker/client/doc.go, line 95 at r1 (raw file):
Previously, willdonnelly (Will Donnelly) wrote…
Also here.
Done.
Give particular focus to fragment reads, surfacing the number of
client-initiated fragment reads and related size metrics.
This change is