opentracing/specification
View on GitHub ↗ ★ 1,166 archived
A place to document (and discuss) the OpenTracing specification. 🛑 This project is DEPRECATED! https://github.com/opentracing/specification/issues/163
4 mentions on Hacker News by 4 people: 0 stories, 4 comments · first 2017-07-24 · latest 2024-06-14
20082026
-
…traces_ whereas as you point out there are cases where you want correlation _within a trace_. [0]: https://github.com/opentracing/specification/issues/142
comment by diurnalist · 2024-06-14 · in The problem with OpenTelemetry -
…since it's, well, cross-language. There is an open issue about Envoy/linkerd/Istio support here: https://github.com/opentracing/specification/issues/86 (as well as in a number of other locations) As an OpenTracing contributor, the core…
comment by el_bhs · 2017-09-25 · in Jaeger – A Distributed Tracing System -
…one per language, with common semantics. Should it be about a wire protocol instead? Discussion at https://github.com/opentracing/specification/issues/34
comment by paulddraper · 2017-09-25 · in Jaeger – A Distributed Tracing System -
…to spans in a standard way (this lets any opentracing-compatible UI display/search errors etc): https://github.com/opentracing/specification/blob/master/sem... OpenTracing also allows you to define functions that follow each other:…
comment by tonyhb · 2017-07-24 · in The future of latency profiling in Go