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
Some of the retry metrics are specified in a little unclear way:
ft.<name>.retry.callsSucceededNotRetried.total: The number of times the method was called and succeeded without retrying ft.<name>.retry.callsSucceededRetried.total: The number of times the method was called and succeeded after retrying at least once ft.<name>.retry.callsFailed.total: The number of times the method was called and ultimately failed after retrying
In all cases, the text seems to assume that there is no other fault tolerance strategy applied. For example, if there's a fallback strategy, then the method will not "ultimately fail" even though all retry attempts fail.
We should provide more clear specification text here, one that doesn't assume absence of other FT strategies and is only worded in terms of the retry operation and not the ultimate result of the method call.
The text was updated successfully, but these errors were encountered:
Some of the retry metrics are specified in a little unclear way:
ft.<name>.retry.callsSucceededNotRetried.total
: The number of times the method was called and succeeded without retryingft.<name>.retry.callsSucceededRetried.total
: The number of times the method was called and succeeded after retrying at least onceft.<name>.retry.callsFailed.total
: The number of times the method was called and ultimately failed after retryingIn all cases, the text seems to assume that there is no other fault tolerance strategy applied. For example, if there's a fallback strategy, then the method will not "ultimately fail" even though all retry attempts fail.
We should provide more clear specification text here, one that doesn't assume absence of other FT strategies and is only worded in terms of the retry operation and not the ultimate result of the method call.
The text was updated successfully, but these errors were encountered: