[
https://issues.apache.org/jira/browse/ARTEMIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646006#comment-16646006
]
Carsten Lohmann commented on ARTEMIS-2028:
------------------------------------------
The [mailing list
discussion|https://activemq-users.markmail.org/thread/wnhb3hpume2jt57r] a while
back has had the result, that a solution as a broker plugin, kept outside of
the Artemis repo, is seen as the preferred way to implement this (possibly
contributed to "OpenTracing-contrib").
As for the necessary features to implement such a plugin, there's only
ARTEMIS-2045 missing as of now - see
[PR#2256|https://github.com/apache/activemq-artemis/pull/2256].
@[~jbertram]: Do you see a way for someone to have a look at that PR?
> Add OpenTracing support
> -----------------------
>
> Key: ARTEMIS-2028
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2028
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Carsten Lohmann
> Priority: Major
> Attachments: Artemis-OpenTracing.png, Artemis-OpenTracing2.png
>
>
> 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 Artemis.
> 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 would mean more general distributed tracing support than the one
> proposed in ARTEMIS-461.
> To start out with, support could be added to the AMQP protocol, using AMQP
> delivery annotations to get the OpenTracing SpanContext from incoming
> messages and to put the SpanContext into outgoing messages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
