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
As of today, whenever a CPE is connected to talaria during this time we will be emitting the event to caduceus. now the problem here is we get the trace information during the WSS connection but the same trace information is not propagated to Caduceus, in this case when the request is landed at Caduceus with a new trace-id.
Hi Team,
As of today, whenever a CPE is connected to talaria during this time we will be emitting the event to caduceus. now the problem here is we get the trace information during the WSS connection but the same trace information is not propagated to Caduceus, in this case when the request is landed at Caduceus with a new trace-id.
In this piece of code, we are not propagating the trace-id in the event.
https://github.com/xmidt-org/webpa-common/blob/5b1562f062b906e246f6bed801e4e50bbf69a784/device/manager.go#L264
In the future, we can extend this solution to receive the events with trace-id from the CPE and we can delegate the same trace-id to caduceus.
The text was updated successfully, but these errors were encountered: