distributed tracing solutions for vertx

1,457 views
Skip to first unread message

Piero dS

unread,
Oct 27, 2016, 6:02:57 AM10/27/16
to vert.x
Hello,

as the title says, what are the alternatives for distributed tracing with vertx?

thanks

Emmanuel Idi

unread,
Oct 27, 2016, 1:46:43 PM10/27/16
to vert.x
I have zipkin working with vertx[1] v3.2.1 though it required some core updates[2] to get the span maintenance to work out. In particular:

- Eventbus interceptor extended to both intercept message send and delivery
- Needed a "scheduler interceptor" to propagate context across executions (since, obviously, TLS won't work in this context).

Let me know if you're interested in using this. I've been meaning to write-up an issue and PR against the latest release. If I know that there's interest out there, it'll be motivation to move it forward.

-ei

Julien Viet

unread,
Oct 27, 2016, 3:13:23 PM10/27/16
to ve...@googlegroups.com
hi

the core modifications look clean to me and quite simple (without any testing though).

it would be great if Clement which has been studying this could give his opinion about it.

Julien

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/abe03fd2-b5e5-4e5a-9a4c-bae7b89fa0d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mumuney Abdlquadri

unread,
Oct 27, 2016, 4:05:37 PM10/27/16
to ve...@googlegroups.com

On Thu, Oct 27, 2016 at 8:13 PM, Julien Viet <jul...@julienviet.com> wrote:
hi

the core modifications look clean to me and quite simple (without any testing though).

it would be great if Clement which has been studying this could give his opinion about it.

Julien
On Oct 27, 2016, at 7:46 PM, Emmanuel Idi <emmanu...@gmail.com> wrote:

I have zipkin working with vertx[1] v3.2.1 though it required some core updates[2] to get the span maintenance to work out. In particular:

- Eventbus interceptor extended to both intercept message send and delivery
- Needed a "scheduler interceptor" to propagate context across executions (since, obviously, TLS won't work in this context).

Let me know if you're interested in using this. I've been meaning to write-up an issue and PR against the latest release. If I know that there's interest out there, it'll be motivation to move it forward.

-ei

[2] https://github.com/emmanuelidi/vert.x/compare/v3.2.1...emmanuelidi:v3.2.1+tracing


On Thursday, October 27, 2016 at 3:02:57 AM UTC-7, Piero dS wrote:
Hello,

as the title says, what are the alternatives for distributed tracing with vertx?

thanks

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/0A6D13C4-36A9-4761-AB16-07E8FEF6533B%40julienviet.com.

Emmanuel Idi

unread,
Oct 27, 2016, 4:14:21 PM10/27/16
to ve...@googlegroups.com
Good to hear, Julien. Once Clement takes a look, and gives feedback, I'll look into getting a PR on vertx-core ready and write up some docs in the vertx-zipkin module on how to use.

-ei

On Thu, Oct 27, 2016 at 12:13 PM, Julien Viet <jul...@julienviet.com> wrote:
hi

the core modifications look clean to me and quite simple (without any testing though).

it would be great if Clement which has been studying this could give his opinion about it.

Julien
On Oct 27, 2016, at 7:46 PM, Emmanuel Idi <emmanu...@gmail.com> wrote:

I have zipkin working with vertx[1] v3.2.1 though it required some core updates[2] to get the span maintenance to work out. In particular:

- Eventbus interceptor extended to both intercept message send and delivery
- Needed a "scheduler interceptor" to propagate context across executions (since, obviously, TLS won't work in this context).

Let me know if you're interested in using this. I've been meaning to write-up an issue and PR against the latest release. If I know that there's interest out there, it'll be motivation to move it forward.

-ei

[2] https://github.com/emmanuelidi/vert.x/compare/v3.2.1...emmanuelidi:v3.2.1+tracing


On Thursday, October 27, 2016 at 3:02:57 AM UTC-7, Piero dS wrote:
Hello,

as the title says, what are the alternatives for distributed tracing with vertx?

thanks

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "vert.x" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vertx/178nTCnJTTU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vertx+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/0A6D13C4-36A9-4761-AB16-07E8FEF6533B%40julienviet.com.

Piero dS

unread,
Oct 27, 2016, 5:07:02 PM10/27/16
to vert.x
Thanks!

Clement Escoffier

unread,
Oct 29, 2016, 9:46:01 AM10/29/16
to ve...@googlegroups.com
Hi,

I just add a quick look, it looks great. By giving such kind of context we can pass “tracing metadata”.  I will do a more in depth check next week. I also need to check how does it work with “worker” (and passing the metadata between an event loop context and a worker context).

Clement

To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.

Michael Remme

unread,
Nov 17, 2016, 9:01:03 AM11/17/16
to vert.x
this would be really great +1
any chance, that it will come with 3.3.4?
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.

-- 
You received this message because you are subscribed to a topic in the Google Groups "vert.x" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vertx/178nTCnJTTU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vertx+un...@googlegroups.com.

Julien Viet

unread,
Nov 17, 2016, 9:03:28 AM11/17/16
to ve...@googlegroups.com
I opened an issue on the original project to ask for this to be contributed to Vert.x Core, so we can move forward on this.

it should be in 3.4 at least (no 3.3.4 planned so far)



Message has been deleted

Emmanuel Idi

unread,
Nov 17, 2016, 11:16:55 AM11/17/16
to ve...@googlegroups.com
Ok, sounds good. I should have some cycles to work on this over the US holiday next week.

To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "vert.x" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vertx/178nTCnJTTU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vertx+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/ED607671-53C8-4FF7-921C-0D7FE31FC46F%40julienviet.com.

Julien Viet

unread,
Nov 17, 2016, 11:22:13 AM11/17/16
to ve...@googlegroups.com
awesome!

Julien Viet

unread,
Nov 18, 2016, 3:37:13 AM11/18/16
to ve...@googlegroups.com
so in Vert.x Core we shall provide the callback necessary to integrate with Zipkin, Opentracing, etc…

then projects can use it to build on top of it.

then we need to make sure that existing solutions integrates with Vert.x Core, wether or not we would host such things under Vert.x Umbrella is not yet determined.

On Nov 17, 2016, at 4:06 PM, jan.ker...@braintags.de wrote:

Zipkin integration sounds like a really good :) 
Any plans on later maybe switch to http://opentracing.io/ ? Shouldn't be to hard to switch it. Once a kind of context is available. This would allow the users to plug in the traceing library they want, something similar like with you did with the loggers.

James Adams

unread,
Nov 18, 2016, 11:39:04 AM11/18/16
to vert.x
Very pleased to hear this!

I recently posted a question about a distributed logging context (https://groups.google.com/forum/#!topic/vertx/9rHzX3vVg8Y) and was directed here.

I've been working on a crude interim solution for distributed logging correlation which lacks exactly this "vertx processing context" and so we are having to pass a logger instance through our codebase which is messy and still impossible to capture log output within dependencies. 
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "vert.x" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vertx/178nTCnJTTU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vertx+un...@googlegroups.com.

Michael Krumm

unread,
Dec 1, 2016, 2:28:53 AM12/1/16
to vert.x
Instana automatically traces vert.x distributed and cross language - no configuration or code edit needed. More information on the Tracing approach, supported technologies and frameworks as well as customization possibilities (e.g. SDK) are available here: https://instana.atlassian.net/wiki/display/DOCS/Tracing

We also support OpenTracing - in case you already implemented that.

You can find more information about Instana at www.instana.com.
And an introduction webinar at https://www.youtube.com/watch?v=Ar2c12aDABg

If you have any questions: happy to answer them anytime.

Vinay Samudre

unread,
Dec 20, 2016, 7:37:24 PM12/20/16
to vert.x
Hi Mumuney,

I tried using open tracing api from out app, I am getting following error:

WARNING: [BatchTraceReporter] [Thread[vert.x-worker-thread-58,5,main]] Trace publisher is not available!

Please help


On Friday, October 28, 2016 at 7:05:37 AM UTC+11, Mumuney Abdlquadri wrote:
On Thu, Oct 27, 2016 at 8:13 PM, Julien Viet <jul...@julienviet.com> wrote:
hi

the core modifications look clean to me and quite simple (without any testing though).

it would be great if Clement which has been studying this could give his opinion about it.

Julien
On Oct 27, 2016, at 7:46 PM, Emmanuel Idi <emmanu...@gmail.com> wrote:

I have zipkin working with vertx[1] v3.2.1 though it required some core updates[2] to get the span maintenance to work out. In particular:

- Eventbus interceptor extended to both intercept message send and delivery
- Needed a "scheduler interceptor" to propagate context across executions (since, obviously, TLS won't work in this context).

Let me know if you're interested in using this. I've been meaning to write-up an issue and PR against the latest release. If I know that there's interest out there, it'll be motivation to move it forward.

-ei

[2] https://github.com/emmanuelidi/vert.x/compare/v3.2.1...emmanuelidi:v3.2.1+tracing


On Thursday, October 27, 2016 at 3:02:57 AM UTC-7, Piero dS wrote:
Hello,

as the title says, what are the alternatives for distributed tracing with vertx?

thanks

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.

Vinay Samudre

unread,
Dec 20, 2016, 8:04:23 PM12/20/16
to vert.x
After adding following dependency warning went away, but I cant see anything in AMP console, am i missing obvious?

Vinay Samudre

unread,
Dec 20, 2016, 8:05:52 PM12/20/16
to vert.x
After adding following dependency warning went away, but I cant see anything in AMP console, am i missing obvious?

 @Grab(group='org.hawkular.apm', module='hawkular-apm-trace-publisher-rest-client', version='0.13.0.Final')

Vinay Samudre

unread,
Dec 21, 2016, 11:05:06 PM12/21/16
to vert.x

Resolved - it was build issue, but how can i send context info?
Reply all
Reply to author
Forward
0 new messages