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
The Updater logs when it has more work to do after updating a test group (with 'more = true' in the log line), but it'd be nice to have a metric that allows us to track if there are spikes in groups that don't update, or a consistent line of groups that can't catch up on repeated updates. (This is expected in small numbers because some group updates, especially for new groups, take a long time, but it's a bad sign if this climbs or stays high).
The text was updated successfully, but these errors were encountered:
@michelle192837 Can this be solved by making a map and every time the update function returns an error, we log the results in our map. Plus we can include a counter to it.
We actually have a standard metrics interface use throughout components that can be used for this! We just need to add that to the list of metrics tracked, and increment at the right time.
The Updater logs when it has more work to do after updating a test group (with 'more = true' in the log line), but it'd be nice to have a metric that allows us to track if there are spikes in groups that don't update, or a consistent line of groups that can't catch up on repeated updates. (This is expected in small numbers because some group updates, especially for new groups, take a long time, but it's a bad sign if this climbs or stays high).
The text was updated successfully, but these errors were encountered: