You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Carsten Lohmann (JIRA)" <ji...@apache.org> on 2018/07/25 12:04:00 UTC

[jira] [Created] (DISPATCH-1088) Add OpenTracing support

Carsten Lohmann created DISPATCH-1088:
-----------------------------------------

             Summary: Add OpenTracing support
                 Key: DISPATCH-1088
                 URL: https://issues.apache.org/jira/browse/DISPATCH-1088
             Project: Qpid Dispatch
          Issue Type: New Feature
            Reporter: Carsten Lohmann


In order to get an overview of the lifetime of a message going through different messaging components, it would be good to have support for distributed tracing in the dispatch router.
 The [OpenTracing|http://opentracing.io/] standard defines an API for this, facilitating the use of different (OpenTracing-compatible) tracing systems (e.g. [Jaeger|https://jaegertracing.io/]).

This will mean identifying the different steps of the message processing inside the router and creating/finishing corresponding (child-)_Span_s for it (see [OpenTracing semantic spec|https://github.com/opentracing/specification/blob/master/specification.md]).

As for the implementation, there is an [OpenTracing API for C++|https://github.com/opentracing/opentracing-cpp].

Some more pointers:
 - [Example for loading the tracer library dynamically|https://github.com/opentracing/opentracing-cpp/blob/master/example/dynamic_load/dynamic_load-example.cpp] (corresponding [PR|https://github.com/opentracing/opentracing-cpp/pull/45])
 This approach is supported by Jaeger now as well.
 - [Jaeger C++ OpenTracing binding|https://github.com/jaegertracing/jaeger-client-cpp]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org