opentracing/specification
A place to document (and discuss) the OpenTracing specification. 🛑 This project is DEPRECATED! https://github.com/opentracing/specification/issues/163
Apache-2.0
Pinned issues
Issues
- 33
Standard Interchange Format for OpenTracing
#64 opened by tedsuo - 1
- 2
- 1
- 49
- 1
provide a read API to access *all* baggage items
#12 opened by bhs - 5
Example application
#56 opened by pavolloffay - 6
- 1
- 25
Different licenses
#61 opened by pavolloffay - 3
- 12
- 22
Add a log level [and namespace] in the API
#57 opened by tahini - 20
- 9
What should we be specifying?
#34 opened by paulcleary - 80
Standard(s) for in-process propagation
#23 opened by yurishkuro - 2
- 7
Wire format for MockTracer
#70 opened by pavolloffay - 5
Key Metrics for Tracing Systems
#65 opened by lookfwd - 35
- 21
- 2
- 3
Component hostname
#60 opened by gkumar7 - 7
If I want to define a record like zipkin's service name, which tag i should select?
#58 opened by ruinanchen - 4
- 3
Introduce peer.address standard tag
#16 opened by bhs - 0
- 2
New reference type to support batch scenarios
#52 opened by objectiser - 4
- 8
- 0
Encourage response instrumentation
#43 opened by JonathanMace - 23
error.description standard tag
#29 opened by pavolloffay - 5
Supporting Linux Perf events with Opentracing
#36 opened by hkshaw1990 - 8
How to process a nested RPC framework?
#18 opened by wu-sheng - 3
- 22
- 4
TraceId / SpanId data types
#31 opened by boyand - 7
Clarification of HTTP_HEADERS format requirements
#15 opened by bhs - 4
Build OpenTracing reviewer team?
#30 opened by wu-sheng - 2
- 2
- 1
- 0
feature request: inter-trace references
#17 opened by bhs - 0
- 1
- 0
Define more standard tags in the future?
#13 opened by bhs - 16
How can a tracer append data to an existing span, i.e. span ID that was created in another process
#3 opened by opentracing-importer - 0
What to do about Span.info() / Span.error()
#7 opened by bhs - 31
- 19