-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Feature: Implement @jambonz/tracing library #311
base: main
Are you sure you want to change the base?
Conversation
9616c55
to
177cd4b
Compare
I'm not quite clear on how this works. You've added two new files but no changes to tracer.js and I can't see these files referenced anywhere |
also can you confirm this works with inbound calls as well as REST api triggered outdials? |
SipPropagator works similar to B3Propagator. here Using the extract method to return a Context which then is used to create the span. I mean I could simply do the following in the call-tracer.js file
But it seemed cleaner to do the extracting of traceId, spanId in the SipPropagator class. I haven't hooked this into the tracer config but I suppose that could be the next natural step. Then instead of manually instantiating SipPropagator we could just leverage What are your thoughts? Unless I have completely missed the mark here. I haven't tested REST calls yet, I will update the PR once tested. |
…feature/override-trace-id # Conflicts: # lib/utils/call-tracer.js # tracer.js
@davehorton Can you confirm that the traces for outbound REST calls were successfully being propagated before this PR? I have a feeling they wasn't as all outbound calls (regardless whether INBOUND or REST initiated the call) have a trace id of "0000000000000000" - I think there is an underlying bug here separate to this PR. |
can you set this PR to draft status for now? |
added logger to root spans
-added loglevel
added logger to root spans
-added loglevel
…feature/override-trace-id
@davehorton I just rebased but am unsure if I implemented correctly. let me know if I need to redo. Thanks |
Move tracing to a new library and implement into Feature Server.
X-Trace-ID | X-Span-ID
from Sip HeaderX-Trace-ID | X-Span-ID
to outgoing sip headersExample Trace