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
When making HTTP requests with random (invalid) paths to the HTTP adapter or device registry, these paths will be used as span names for the HTTP request traces.
This will pollute the "operation" combo-box in the Jaeger UI with these names.
This was introduced by the changes made for #3213.
The text was updated successfully, but these errors were encountered:
HTTP requests for which no specific route matches
shall get a fixed tracing span name, not one
corresponding to the request path.
Signed-off-by: Carsten Lohmann <[email protected]>
HTTP requests for which no specific route matches
shall get a fixed tracing span name, not one
corresponding to the request path.
Signed-off-by: Carsten Lohmann <[email protected]>
When making HTTP requests with random (invalid) paths to the HTTP adapter or device registry, these paths will be used as span names for the HTTP request traces.
This will pollute the "operation" combo-box in the Jaeger UI with these names.
This was introduced by the changes made for #3213.
The text was updated successfully, but these errors were encountered: