[
https://issues.apache.org/jira/browse/ARTEMIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873660#comment-16873660
]
Michael Andre Pearce edited comment on ARTEMIS-2028 at 6/26/19 9:15 PM:
------------------------------------------------------------------------
As per outcome on mailing list, as like other plugins that third parties make,
they sit with the third party. this was the outcome of the discussion on the
mailing list, was to discuss with OpenTracings project and host this in
OpenTracing's contribs.
was (Author: michael.andre.pearce):
As per outcome on mailing list, as like other plugins that third parties make,
they sit with the third party. this was the outcome of the discussion on the
mailing list.
> 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)
