[
https://issues.apache.org/jira/browse/ARTEMIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584304#comment-16584304
]
Justin Bertram commented on ARTEMIS-2028:
-----------------------------------------
I think the best approach right now would be the least invasive (i.e. using
interceptors & plugins). As far as where the code itself should live I think
it's worth asking the broader community on the [user mailing
list|http://activemq.apache.org/mailing-lists.html]. Can you send an email to
the user list with a subject something like "[DISCUSS] OpenTracing in Artemis"?
Propose the general idea, describe the benefits, & ask where the code should
live.
> 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)
