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 new telemetry support largely works well, but while experimenting, I found that trace data is missing for any response that is not generated due to routing; this include the resource and file interceptors, and perhaps others.
We should find a way for such interceptor to communicate (via a context key) that they generated a response, even if it wasn't routed, that can be used by the request tracing interceptor to generate a reasonable name for the trace.
The text was updated successfully, but these errors were encountered:
The new telemetry support largely works well, but while experimenting, I found that trace data is missing for any response that is not generated due to routing; this include the resource and file interceptors, and perhaps others.
We should find a way for such interceptor to communicate (via a context key) that they generated a response, even if it wasn't routed, that can be used by the request tracing interceptor to generate a reasonable name for the trace.
The text was updated successfully, but these errors were encountered: