feat(ConsoleSpanExporter): export span links #2917
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
Currently the ConsoleSpanExporter does not include Span links, if the span happens to have any.
Short description of the changes
This PR adds
span.links
to the exported info.As well, this changes the exporter to use
console.dir(...)
instead ofconsole.log(...)
so that the objectdepth
can be set to 3, instead of the default 2. It is the difference between this (withconsole.log
):and this (console.dir with depth 3):
This does mean an additional
links: []
in the output of each span for the common case where there are no links. However, given ConsoleSpanExporter is for dev/debugging, that slight additional noise doesn't seem bad.Type of change
How Has This Been Tested?
Besides running this manually:
I also updated ConsoleSpanExporter.test.ts to expect a "links" key in the output.
Checklist:
Documentation has been updated