Can you explain a bit more the model used for sending/consuming the trace data and how long does the data is supposed to stick around? Does it follow a pub/sub model? If the data sticks around awhile then a traditional message broker might not be the greatest option as messages are meant to be consumed pretty quickly rather than accumulating in a queue. Once messages start accumulating you start running into performance degradation due to paging.
As far as I know RabbitMQ doesn't have its own messaging transport (unlike Kakfa). It was built around AMQP so if the RabbitMQ integration is using AMQP 1.0 then it should be pretty simple to also integrate with ActiveMQ 5.x and/or ActiveMQ Artemis or any other broker that supports AMQP 1.0. It appears from the discussions on GitHub that the 5.x broker is being targeted. However, for what it's worth, ActiveMQ Artemis is slated to become ActiveMQ 6 once it reaches sufficient feature parity. Justin On Mon, Mar 25, 2019 at 7:27 PM Adrian Cole <[email protected]> wrote: > Hi, all. > > The Apache Zipkin(incubating) project allows distributed tracing by > sending trace identifiers in application payloads usually as headers, with > timing data sent out of band often by a messaging transport like RabbitMQ > and Kafka. We have some community interest in supporting ActiveMQ also, > including an implementation. This would mean that apps would implicitly > send trace data over an ActiveMQ connection and that Zipkin server would > poll that on the other side. This is particularly a big decision for us as > we are considering ActiveMQ as an out-of-box feature. > > As Zipkin is for distributed tracing, that means potentially many > languages, at least java, go, ruby, php, python etc. The libraries needed > to support this are not a lot of code, but something we'd want to maintain. > I know there are a couple ways to use ActiveMQ, and possibly some > constraints or version concerns of interest. If anyone has feedback on > using ActiveMQ to move distributed trace data, please add your points of > interest here. This could be of advice nature, or that you would use it, or > otherwise > > issue: https://github.com/openzipkin/zipkin/issues/1990 > work in progress server integration: > https://github.com/openzipkin/zipkin/pull/2466 > work in progress java-tracer integration: > https://github.com/openzipkin/zipkin-reporter-java/pull/136 >
