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
Describe the feature:
Support trace context propagation and traceID visibility
Describe a specific use case for the feature:
The client must pass the trace context with each request to ensure the trace can be propagated across all downstream services. Additionally, when a request fails or encounters an error, the client needs the ability to log or display the specific traceID associated with the failed request.
This capability allows developers and operators to:
Identify the exact trace path of the failed request across the system.
Debug and pinpoint the root cause of the error by correlating logs and metrics using the traceID.
Provide observability and insight into client-side request behaviors in the context of the broader system.
For example, if a client makes a request to Milvus service and receives an error response, the client can log the traceID from the trace context. This traceID can then be used to investigate the issue in distributed tracing tools, enabling quick identification of which service in the chain caused the failure.
The text was updated successfully, but these errors were encountered:
Describe the feature:
Support trace context propagation and traceID visibility
Describe a specific use case for the feature:
The client must pass the trace context with each request to ensure the trace can be propagated across all downstream services. Additionally, when a request fails or encounters an error, the client needs the ability to log or display the specific traceID associated with the failed request.
This capability allows developers and operators to:
For example, if a client makes a request to Milvus service and receives an error response, the client can log the traceID from the trace context. This traceID can then be used to investigate the issue in distributed tracing tools, enabling quick identification of which service in the chain caused the failure.
The text was updated successfully, but these errors were encountered: