Open butonic opened 4 years ago
@TheOneRing effort estimation? Should this be part of the client or should this be better a Qt thingy?
Ah, they have a C++ library: https://github.com/open-telemetry/opentelemetry-cpp
There would also be https://api.kde.org/frameworks/kuserfeedback/html/index.html (not related to open-telemetry)
Ah, they have a C++ library: https://github.com/open-telemetry/opentelemetry-cpp
Its just a bunch of empty folders at the moment.
opencensus has merged with opentracing into opentelemetry. maybe they will continue to use the opencensus stuff in https://github.com/census-instrumentation/opencensus-cpp in ocis / reva we currently use opencensus, but will switch once telemetry is becoming stable.
IMHO this doesn't really make sense for clients, this only makes sense for complex micro service architectures where it's hard to debug the flow of requests.
What exactly is the client supposed to log? I believe logging request would be better done on the server side.
W3C specification that defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios: https://www.w3.org/TR/trace-context/#examples-of-http-traceparent-headers
https://opentelemetry.io/ allow tracing requests from client to server.