Linking spans across network boundaries can be a bit tricky, but it is definitely possible. Your ...
Has anyone managed to link spans across network boundaries?
I have a service that processes "Stage1" and "Stage2" pubsub messages.
"Stage1" will end up publishing one or more "Stage2" messages.
I'd like to link all of the spans for "Stage2" messages to the "Stage1" message that created them. My initial thought was:
* Include "Stage1"'s span id in all the "Stage2" messages that it generates
* When processing "Stage2", link the "Stage2" span using the "Stage1" id that we added to the message
However, I cannot for the life of me figure out how to link the spans using just the "id". I fear I may be missing something obvious...has anyone done this before or come across any examples of doing this?
I have a service that processes "Stage1" and "Stage2" pubsub messages.
"Stage1" will end up publishing one or more "Stage2" messages.
I'd like to link all of the spans for "Stage2" messages to the "Stage1" message that created them. My initial thought was:
* Include "Stage1"'s span id in all the "Stage2" messages that it generates
* When processing "Stage2", link the "Stage2" span using the "Stage1" id that we added to the message
However, I cannot for the life of me figure out how to link the spans using just the "id". I fear I may be missing something obvious...has anyone done this before or come across any examples of doing this?
