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
Below is a rough sketch of how our SpringBoot microservices communicate with a Remote Blockchain app, which triggers events based on the requests send to it. The blockchain can generate multiple events for a single request, and this triggers multiple Traces to be generated on the auto-instrumented event Listening service "C"
Please suggest how can we combine these multiple traces on the receiving side with the original trace that was generated at the start of the flow. A few points about our service that might give better clarity :
At the start of the flow, we are generating a unique msg-id that is used to correlate the logs, and it flows through all the microservices.
Perhaps we serialize the context in service "B", just before hitting the blockchain, and then when service "C" receives events from the blockchain, we use the msg-id to fetch the related span context from DB/File and create a child span out of that? will that "unite" the traces?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Below is a rough sketch of how our SpringBoot microservices communicate with a Remote Blockchain app, which triggers events based on the requests send to it. The blockchain can generate multiple events for a single request, and this triggers multiple Traces to be generated on the auto-instrumented event Listening service "C"
Please suggest how can we combine these multiple traces on the receiving side with the original trace that was generated at the start of the flow. A few points about our service that might give better clarity :
Beta Was this translation helpful? Give feedback.
All reactions