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
We have more than one interceptor which asks the user to register it as the first interceptor in their list of interceptors. This seems like a non-sustainable pattern in the long run.
The text was updated successfully, but these errors were encountered:
The two examples of this that we found were ORCA and OpenCensus instrumentation.
OC "needs" to be first because it won't include anything before it in the call latency. This is not super critical, but useful to get accurate metrics.
ORCA "needs" to be first because any interceptors that want to set metrics would need to come later. This is only relatively critical.
We can update the docstrings here, but AFAIK there's no way around the fact that ORCA is injected via an interceptor and OC starts timing when its interceptor is invoked.
We have more than one interceptor which asks the user to register it as the first interceptor in their list of interceptors. This seems like a non-sustainable pattern in the long run.
The text was updated successfully, but these errors were encountered: