-
Notifications
You must be signed in to change notification settings - Fork 102
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
Combine reducer and incremental update duration metrics #1168
Comments
I think this is the combined metrics that we already have -
|
@Shubham8287 I'd like to only account for transaction processing time vs the entire time spent on the server. I believe that metric tracks the latter, although correct me if I'm wrong. |
You are right, this metric measure entier time spent. |
Right now reducer durations and incremental update durations are tracked using two different metrics. We should also have a metric that combines them since a reducer call and an incremental update are logically an atomic unit of execution.
This will give users additional observability into their reducers as they'll be able to see which reducers have more expensive incremental updates.
Note this will be a natural fallout of #1157 since both will be executed as part of the same transaction, but we'll want to make sure to maintain the separated metrics as well.
The text was updated successfully, but these errors were encountered: