zipkin and nginx/haproxy

[Joe Crobak]

We're using nginx as a reverse proxy and are looking to integrate it with zipkin. Has anyone done this? The solution I'm currently planning is to log timing information (start of request, end of request, length of upstream request) and consume that data in a separate process to approximate the sr, cs, cr, ss events.

If someone has implemented (or can think of) a better solution, it'd to hear.

Thanks,

Joe

[hacfi]

Hi Joe,

have a look at http://itszero.github.io/blog/2014/03/03/introduction-to-twitters-zipkin/ . It’s explained there but haven’t tried it yet.

[Joe Crobak]

Hi,

Thanks for sending over the link. I find it really useful conceptually*, but it doesn't seem to have any technical details of instrumenting nginx.

Best,

Joe

* it'd be great if the zipkin docs themselves had a good overview like this one... or maybe linked to it.

--

---
You received this message because you are subscribed to the Google Groups "zipkin-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zipkin-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Smick]

Better documentation has long been on my TODO list. Unfortunately it keeps getting bumped for higher priority things.

You can dig around in Finagle's implementation and follow its model [1]. Essentially Zipkin needs a Span struct filled in with Annotations that mark when a request is received or sent and when a response is received or sent. There's a method in Trace.scala [2] that shows how this is handled.

I've created an issue as a reminder to myself: https://github.com/twitter/zipkin/issues/401

1) https://github.com/twitter/finagle/tree/master/finagle-core/src/main/scala/com/twitter/finagle/tracing

2) https://github.com/twitter/finagle/blob/master/finagle-core/src/main/scala/com/twitter/finagle/tracing/Trace.scala#L191-L203

--
Jeff Smick

@sprsquish