You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resyncs trigger reprocessing of Work objects that haven't changed and this ends up generating unrealistic work_apply_time_seconds because this metric is based on a timestamp set on an annotation whenever the Work object was created/updated, so we end up with metrics that always hit the maximum bucket limits and are not really useful.
The text was updated successfully, but these errors were encountered:
@sschepens, thank you for the issue. You are right, that specific metrics will increase even when the work is not changed. I can think of a few ways to improve it. For example, we can only increase this if there is change. I think most of the functionality is there, I wonder if you want to give it try?
Describe the bug
Resyncs trigger reprocessing of Work objects that haven't changed and this ends up generating unrealistic
work_apply_time_seconds
because this metric is based on a timestamp set on an annotation whenever the Work object was created/updated, so we end up with metrics that always hit the maximum bucket limits and are not really useful.The text was updated successfully, but these errors were encountered: