[
https://issues.apache.org/jira/browse/ARTEMIS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-461.
------------------------------------
Resolution: Information Provided
The recommendation here is to implement tracing support using a plugin (as was
recommended for OpenTracing support as well on ARTEMIS-2028).
> add a zipkin plugin for distributed tracing of message based applications
> -------------------------------------------------------------------------
>
> Key: ARTEMIS-461
> URL: https://issues.apache.org/jira/browse/ARTEMIS-461
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: James Strachan
> Priority: Major
>
> zipkin is an awesome distributed tracing system:
> http://zipkin.io/
> its already integrated into various things like jaxrs and http:
> https://github.com/openzipkin/brave/tree/master/brave-jaxrs2
> https://github.com/openzipkin/brave/tree/master/brave-http
> along with camel:
> https://github.com/apache/camel/tree/master/components/camel-zipkin
> it'd be nice of we could trace requests which are made across ActiveMQ
> Artemis too so we could generate nice trace diagrams like this:
> http://zipkin.io/public/img/web-screenshot.png
> mostly this means having the ability to replicate Zipkin headers from an
> inbound message to outbound messages for the same Session so that the zipkin
> breadcrumbs can flow across messaging along with http / jaxrs / camel etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
