-
Notifications
You must be signed in to change notification settings - Fork 805
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
Adding more metrics, fix some bugs #965
Conversation
* Adding more metrics * Fix bugs in retry policy
logging.TagFirstEventID: request.GetFirstEventId(), | ||
logging.TagNextEventID: request.GetNextEventId(), | ||
}) | ||
|
||
r.metricsClient.RecordTimer( |
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 seems strange to report replication events size as a timer which is generally used for computing latencies. Is the intention here to compute various percentiles for this counter?
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.
yes, i would like to get the distribution of the number of events per replication task, this can be useful for debugging or explaining the potential high latency issue
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.
Looks good.
Let's check if the metric can be converted to a guage, as it makes more sense.
If not then you can use timer metric.
solve #941