New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add ConsoleSpanExporter #300
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could create an issue in order to discuss if having a hierarchy between spans that have the same traceid and traceid/parentSpanId would help to diagnose possible issues. WDYT?
I don't expect users to use ConsoleExporter in the production system. I think creating a hierarchy in the console would be a little tricky job and not sure whether it is worst to spend time on that. WDYT? |
): void { | ||
for (const span of spans) { | ||
console.log( | ||
`{name=${span.name}, traceId=${span.spanContext.traceId}, spanId=${ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to use the .toString
function on Span
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is actually ReadableSpan
interface. I am not sure how to add methods on the interface
…elemetry#303) Signed-off-by: isayme <isaymeorg@gmail.com>
Which problem is this PR solving?
Short description of the changes