Use either get_span_context() or context() for both Span/Link
See original GitHub issueSpan has get_span_context()
whereas Link
exposes it as a context
property.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
opentelemetry.trace package
The OpenTelemetry tracing API describes the classes used to generate distributed traces. The Tracer class controls access to the execution context, and manages ......
Read more >OpenTelemetry.Trace.Core - Hackage
A span contains a span context, which is a set of globally unique identifiers that represent the unique request that each span is...
Read more >Span (opentelemetry-api-trace 0.13.1 API) - javadoc.io
SpanContext, getSpanContext(). Returns the SpanContext associated with this Span . boolean, isRecording(). Returns true if this Span records tracing events ...
Read more >java - How to create Context using traceId in Open Telemetry
service1: Writing traceId in sqs message user attribute traceId=Span.current().getSpanContext().getTraceId() · service2: Reading traceId from sqs ...
Read more >Figure out how to link services using manual instrumentation
@Get('/sendMessage') async sendMessage(@Headers() requestHeaders: any) { const activeSpanContext = trace.getSpanContext(context.active()) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@carlosalberto Would it not look weird to have an api method
get_span_context()
on aLink
but a property getter forattributes
?I don’t think the change provides TOO much benefit so I feel we should just leave them. Closing this.