6 ms·
Jaeger – A Distributed Tracing System
- secure 9y agoI recently used Jaeger to visualize what my distributed system is doing. Got it done in about 2 hours; pretty pleased with that. Jaeger is visually pleasing, available via docker and just worked for me.
- jpkrohling_jpk 9y agoWould you be interested in writing a guest blog post about it?
- pat2man 9y agoI've been using Jaeger for a few months now and it performs really well. I even wrote a custom tracer for an unsupported language and it was relatively straight forward. There are a few things I wish it did, but they are all on the roadmap: http://jaeger.readthedocs.io/en/latest/roadmap/ http://jaeger.readthedocs.io/en/latest/roadmap/
- ocharles 9y agoCan you share that custom tracer? I'd be interested in seeing that.
- jpkrohling_jpk 9y agoIf you are interested in contributing it to the jaegertracing GitHub repository, I'm sure the Jaeger community would welcome it :)
- jhinds 9y agoNeat! I was looking into tracing solutions for our k8s cluster the other day and was going to look into setting up Zipkin. Now I'll this to my list of tools to evaluate. I found this blog post by uber informative https://eng.uber.com/distributed-tracing/ https://eng.uber.com/distributed-tracing/ so maybe there is no need to even setting up Zipkin and just start with Jaegar?
- weitzj 9y agoI am evaluating Google Stackdriver as well, with a zipkin collector. Will see...
- dankohn1 9y agoMost folks will choose either Zipkin or Jaeger, but both are OpenTracing-compatible distributed tracing systems. You might find the Cloud Native Landscape useful for thinking about the options: https://github.com/cncf/landscape/blob/master/README.md https://github.com/cncf/landscape/blob/master/README.md Disclosure: I’m the executive director of CNCF, which just adopted Jaeger 2 weeks ago, and I’m an author of the landscape.
- muninn_ 9y agoI have used that landscape document as a very informative point of reference for the last couple of months. Thank you for creating it.
- dankohn1 9y agoYou're very welcome. You cannot imagine the amount of criticism it has engendered.
- dastbe 9y agoHow do you plan on keeping it sane over time? Even disregarding paring down the number of times managed major providers appear on the list (which is super sensible imo), won't it start to get quite crowded with all the open source competitors appearing?
- dankohn1 9y agoThe guidelines we're following are at: https://github.com/cncf/landscape#cloud-native-landscape-project https://github.com/cncf/landscape#cloud-native-landscape-pro... The CNCF storage WG is also looking at creating a "zoomed in" version of the storage section with higher fidelity information. That's one model of providing more detail. We also have an interactive version of the landscape coming that will provide filtering, zooming, etc.
- shevy 9y agoI don't like the name. For those who don't know german, Jaeger is "Jäger" is hunter/ranger. A somewhat neutral term in itself but there is also a slight, somewhat remote connection towards some part of the history ("Jagdstaffel" and what not). I have absolutely no idea if this has anything to do with it, mind you - but since the main authors appear to be in the USA, I find that very awkward. Why not just stick to some english name? That would seem a much better it. Or perhaps they think german names are awesome ... it's also weird when you see all the people write Jaeger rather Jäger...
- pebers 9y agoApart from the pop-culture references others have mentioned, the top Google search result is a fairly well-known fashion brand (https://www.jaeger.co.uk https://www.jaeger.co.uk), I don't think anyone is that bothered by it. I'd guess the reason for using Jaeger vs. Jäger is simply that the former is much easier to type on many keyboards. You might be reading a bit more into it than is warranted.
- santaclaus 9y agoTotally should have gone with meister for the name instead.
- fs111 9y agowhich means "master" in English and then you end up in the master/slave discussion...
- jjjensen90 9y agoThis is a pretty silly objection. There are plenty of software projects named from a variety of languages not native to the creator of the package. And Jäger has so many neutral meanings and even for a German wouldn't first bring thoughts of the Jagdstaffel I don't think... Also writing the ä as ae is very common for those who have keyboards without umlaut characters... I've seen it lots of times and doesn't look too weird.
- 9y ago
- khc 9y agoIs it something similar to sysdig?
- pritianka 9y agoSysdig is focused on the networking layer. This is for the application layer (L7).
- apurvadave 9y agoActually sysdig can do application, container, host, network. Most of sysdig use cases tend to be more focused on the software running on a node vs the network itself.
- marknadal 9y agoDoes this run in production or is it used for testing? We wrote a distributed testing system ( https://github.com/gundb/panic-server https://github.com/gundb/panic-server ), so I'm trying to understand if integrating Jaeger would be helpful. If Jaeger is run on a production stack, I'd be curious to understand how that works (are there any tech talks on it yet?). If it is designed to run for tests, that makes sense, but then does it depend upon another distributed testing tool? If so, I'd love to see that tool. Glad to see it be Open Sourced!!!
- richdougherty 9y agoIt's a production tracing tool, but you could run it in a testing environment too.
- javajumbo 9y agoYes, Jaeger is used in production at Uber and many other companies. Our original blog post on the history of Jaeger: https://eng.uber.com/distributed-tracing/ https://eng.uber.com/distributed-tracing/
- necubi 9y agoI'm disappointed that all of the open-source tracing systems have adopted the Dapper [0] model. It's understandable why: it's extremely simple to implement, as it handles scaling challenges by doing client-side sampling. A bit of background about how Dapper-style distributed tracing works. Things typically start with an RPC call of some kind (typically from an external source like a public load balancer). At that point, you must decide whether to trace this request or not, which is typically done as a random sample (say, 1% of requests). At that point, the request gets assigned a _trace id_, a random identifier for that request. The trace id is stored in some request context and propagated to each subsequent service. Each service, meanwhile, divides up its request processing flow into a series of "spans" which represent some piece of computation. For example, a span cover an RPC call or a DB query. Spans are identified by a random _span id_. Once a request has been sampled, all spans for that request are sent to a central span collector where they're stored for later querying. This model is simple but very limited. It's often hard to know whether a trace is interesting at the outset, hence the reliance on random sampling. For example, you might want to understand why your 99p latency is high, but if you're just sampling 1% the 99p requests will only be 0.01% of your sample. More generally, interesting events (like errors or slow requests) tend to be rare, and sampling a random, small percent of requests is unlikely to turn up the interesting cases. A better model, as implemented by lightstep [1] (and an in-progress distributed tracer I've been working on) is to collect all spans. Even with very high request volume it's reasonable to store all spans for at least a few minutes. Doing so opens up all sorts of interesting possibilities, because you can start tracing a request at any point during that window. For example, you might want to trace all requests that have errors in them. Or all requests that take longer than a certain time. Or get a google sample of requests across different latency buckets. Or requests that violate some application invariants you've defined. Ultimately, though, distributed tracing is so helpful for understanding complex distributed systems and webs of microservices, and it's exciting to see more open-source competition for zipkin. [0] Dapper is Google's distributed tracing system. The paper (https://research.google.com/pubs/pub36356.html https://research.google.com/pubs/pub36356.html) kicked off a lot of interest in distributed tracing in the broader community. [1] http://lightstep.com/ http://lightstep.com/
- the_evacuator 9y ago
- trimbo 9y agoIs there a pros/cons comparison to Zipkin? Browsed the docs and couldn't find anything.
- javajumbo 9y agoThere is a section in the CNCF proposal: https://github.com/cncf/toc/blob/master/proposals/jaeger.adoc https://github.com/cncf/toc/blob/master/proposals/jaeger.ado...
- pritianka 9y ago100x better UI among other things. Jaeger has a dedicated team and resources and that shows. They are taking the time to write good docs, build demos, create a thoughtful UI, etc. I definitely recommend it. Being OpenTracing native also helps. Full disclosure, I work on the OpenTracing project.
- saadazzz 9y agoWhat's the performance hit for using Jaeger in production? Are there benchmarks?
- bronz 9y agowhat is tracing?
- fnord123 9y agohttps://en.wikipedia.org/wiki/Tracing_(software) https://en.wikipedia.org/wiki/Tracing_(software)
- manigandham 9y agoIn this context, it's the network-wide version of a stack trace. Instead of just method calls in a process, you take a top-level (HTTP) request and see all the various upstream service calls and their internal logic involved in completing that request. Useful for micro/multi-service based architectures but you can trace anything because it's a standard output format.
- pritianka 9y agoI have to say, you described tracing really well! I work on the OpenTracing project [1] (and at LightStep) and have been describing tracing to people for a while and your explanation is way better haha :-) [1] opentracing.io
- konschubert 9y agoSlightly off topic: It is really interesting how German names have become en vogue in recent years.
- trampi 9y agoShameless plug: A friend of mine, Felix Barnsteiner, wrote a profiler for Java based applications, called stagemonitor [1]. He started working on it in 2013 for his masters thesis. Since then, he steadily worked on it in the company as well as in his spare time. Some months ago, he implemented support for distributed tracing. Stagemonitor implements Open Tracing. It also collects frontend performance data, called end user monitoring. They get correlated automatically. And the best thing about it: stagemonitor is free and open source (APL). Get in touch if you have any questions. [1]: http://www.stagemonitor.org/ http://www.stagemonitor.org/
- laichzeit0 9y agoHow is this different from e.g. AppDynamics or Dynatrace for example? Technically speaking, not free/commercial. From the documentation it doesn't look like much, except probably the biggest downside is that you have to add your instrumentation points manually? i.e. there is code change required.
- jpkrohling_jpk 9y agoJaeger is just the concrete implementation. OpenTracing is what you should think about using when writing your application. That said, you could benefit from automatic instrumentation via OpenTracing framework integration libraries (JAX-RS, Servlets, ...). Or use the Java Agent. But in the end, I think there is value in manually instrumenting your code, specially around your business transactions. This way, you can monitor your business metrics, instead of "http requests" or "cpu load".
- Dowwie 9y agoThis seems like a horror story about a large company that decided to depart from monolithic architectures to one of microservices and found that one set of problems was exchanged for another. Was there a net gain?
- kuwze 9y agoWhy would you use this over a logging framework?