Uh oh!
There was an error while loading. Please reload this page.
feat(opentelemetry): Add addLink(s) to span - #15387
Conversation
size-limit report 📦
|
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
There was a problem hiding this comment.
Nice! This all looks reasonable to me. Just wondered if we're missing something to correctly serialize a span link on the root span to event.contexts.trace?
So basically for a case like
constsomeSpan=startInactiveSpan(...);someSpanContext=someSpan.spanContext();someSpan.end();startSpan({name: 'rootSpan'},()=>{rootSpan.addLink({context: someSpanContext});})(which is probably quite similar to how we'll eventually link previous traces)
| // A general note regarding this test: | ||
| // The fact that the trace_id and span_id are correctly linked is tested in a unit test |
There was a problem hiding this comment.
I also only learned this by chance but if this is about not being able to store the ids in variables to compare: You can pass a function to expect({ transaction }) so that you can write better assertions than just comparing the matching object. See here for an example
Uh oh!
There was an error while loading. Please reload this page.
dcfe159 to
2fb2b9dCompareUh oh!
There was an error while loading. Please reload this page.
addLink(s) to spanaddLink(s) to spanUh oh!
There was an error while loading. Please reload this page.
Link spans which are related. Example: