JaegerTracing

Oct 4, 2018
Mar 26, 2019   |  By Juraci Paixão Kröhling
Jaeger was built from day 1 to be able to ingest huge amounts of data in a resilient way. To better utilize resources that might cause delays, such as storage or network communications, Jaeger buffers and batches data. When more spans are generated than Jaeger is able to safely process, spans might get dropped. However, the defaults might not fit all scenarios: for instance, agents running as a sidecar might have more memory constraints than agents running as a daemon in bare metal.
Jan 18, 2019   |  By Juraci Paixão Kröhling
Jaeger is composed of different components, each potentially running in its own host. It might be the case that one of these moving parts isn’t working properly, causing spans to not be processed and stored. When something goes wrong, make sure to check the items listed here.
Dec 10, 2018   |  By Juraci Paixão Kröhling
The Jaeger Agent is the component that is responsible for receiving the spans from the instrumented application and forwarding it to the Jaeger Collector, so that the data gets appropriately stored.
Nov 1, 2018   |  By Juraci Paixão Kröhling
The month of the #hacktoberfest is over and we could count more than 80 PRs opened and more than 50 issues closed! Read on for a recap of what happened during October.
Oct 1, 2018   |  By Joe Farro
Distributed tracing can capture a wealth of data and has the potential to yield invaluable insights. But, bridging the gap between the ocean of spans and the epiphanies they offer is not yet a solved problem. As of Jaeger 1.7, the ability to compare traces is now available in the Jaeger UI. We are hopeful trace comparisons will facilitate going from data to decisions.
This talk comes from practical experience of running a cloud-based SAAS under Kubernetes for the last two years. Prometheus is good for the big picture view of how things are running, while Jaeger acts like a microscope on the internal workings of your system.
Nov 29, 2017   |  By Estafet Consulting
Shows how a microservices architecture can be instrumented to generate Opentracing events which are monitored and presented using Jaeger. The demo is based on one of our github projects - see estafet.com/github and download the source which runs on minishift.
Nov 28, 2017   |  By Estafet Consulting
Opentracing gives us a standard for recording interactions across a distributed microservice architecture, whilst Jaeger is a monitoring tool that shows us the flow of events. It gives huge insight to both devs and ops teams, and is also a potentially cheaper way of demonstrating compliance with MiFID and GDPR.
Nov 8, 2017   |  By Utah Golang User Group
Learn the basics of OpenTracing and Jaeger and why they are so awesome. Jason Newman, Chief Architect at Weave, presents on how Weave uses OpenTracing and Jaeger to diagnose issues on their micro-service architecture.