Distributed Tracing With Jaeger And OpenTelemetry In Kubernetes

preview_player
Показать описание
How to set up and observe distributed tracing with Jaeger and OpenTelemetry in Kubernetes?

#jaeger #opentelemetry #tracing #kubernetes #k8s

▬▬▬▬▬▬ 😳 Sponsor 😳 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction To Tracing With Jaeger
01:40 Push OpenTelemetry Traces To Jaeger
02:27 Robuta (sponsor)
03:18 Push OpenTelemetry Traces To Jaeger (cont.)
06:37 Explore OpenTelemetry Traces In Jaeger
13:25 Distributed Tracing With OpenTelemetry And Jaeger
15:53 Should You Use OpenTelemetry And Jaeger?
Рекомендации по теме
Комментарии
Автор

Are you using tracing? If you are, what do you use? Jaeger? Grafana Tempo? Something else?

DevOpsToolkit
Автор

You are amazing. Yes, kindly advise that we use Opentelmetry solely for request tracking. Alternatively, we might use it to replace Fluentd's log aggregation and routing functions with Logstash.

swarnapriyajena
Автор

Great video as always! I think it would be awesome if you did a video exploring observability in grafana stack (with grafana cloud, for example, which has a free tier). There, you have Prometheus (metrics), Tempo (traces), Logs (Loki), and Grafana (visualization) all working together. Actually, I think you can correlate all of them and look up traces, metrics and logs through the same dashboard. This is a topic I'm personally very interested in. Thanks for your work

alvarotorres
Автор

Yes, please what are the alternative OSS tracing visualization solutions or commercial soluout there

jeanchindeko
Автор

I'm using a mix of Jaeger and OTEL,
centralized collection from several clusters on a single back-end running ElasticSearch (hot-nodes/warm-nodes) using elastic-cloud operator

juanitoMint
Автор

An important aspect that was not mentioned here is should you have traces for everything constantly? Should you enable when troubleshooting? Should you use samples? Maybe trigger upon errors? Sending and keeping all the tracing data for a big production system can be very expansive, add overhead and is not necessary most of the times.

shalomcohen
Автор

Observability is better when combining metrics, logs and traces. So better to choose Tempo

hossamshehab
Автор

I have 2 basic questions

1. Let's suppose we have implemented the instrumentation of code and we have not deployed the jager maybe for 2 months, in that case, what will happen to the data/traces of opentelemetry? How we are storing and managing the data in open telemetry. And if the system is huge and we are keeping the data, what best practices we can implement for managing storage?

2. How is Kiali different from Jager? If we have istio implemented, then Jager/opentelementry is required?

AnkitKumar-yiir
Автор

Thanks for this one too, Victor. Is there a down side to instrumenting applications by using istio sidecars instread of adding it throughout my codebase? Also, did you get around a video on Jaeger alternatives? I'm specifically thinking about Tempo because we use Loki and Prometheus.

PaulGilowey
Автор

Thanks for making such amazing contents. It rly broaden my horizon. Cheers.

kevinyu
Автор

Congrats on winning devopsdozen award well deserved. I wanted to ask if you could compare jaeger to SigNoz or generally go into SigNoz it looks promising, as an OT solution for all 3 Logs, Metrics and traces. And im still not sure if i should use it, and would like to see an unbiased opinion. (of course the creators are not going to tell you about Potential weaknesses) would greatly appreciate it. Christ bless and save you

christopherreimer
Автор

Great video. If jaeger does a fair job of extracting traces info and reliable then it's good to me, cause it look quite easy to use.

trantrunghieu
Автор

great video, very enlightening to the questions i were getting. i have one question though, when i run docker compose up i only see jaeger-all-in-one on the UI. Running the curl or anything doesn't make the services appear on the UI. Am i missing anything?

tomjosi
Автор

Hey Viktor, great video as always. As an. FYI I don't know if the Gists are meant to be up to date or just a temporary guide, but the 'silly-demo' repo has deviated a quite a bit from the commands you are running (expecting crossplane XRDs to create DBs, no stateful-jaeger files etc_). I understand it's impossible to keep them up to date constantly but maybe you could pin the git clone to the commit you are using in the video.

PooPa-ik
Автор

It would be interesting to compare to grafana tempo being one of the newest additions to the cncf in terms of tracing. In addition to that it would be interesting to know if there are any differences in using different visualization tools vs using Jaeger's built in UI.

WeRRa
Автор

Can u please share an architecture diagram focussing on collector gateway with jaeger plus elastic backend

cresento
Автор

Please showcase open telemetry collector exporting data going into tempo and grafana in the next video, in the middle of setting this up with helm charts

mechrono
Автор

Very neat and clear explanation. Would you please compare jaeger with other commercial APM tools?

avanthaditya
Автор

TEMPO, we want to see OTEL+Tempo by you, Viktor! Everyone in here is thinking of this, right?

johnfli
Автор

Can you answer a question, is it possible to use jaeger + istio, for every request and response event of each microservice? automatic without changing microservice/pod code? How can I look for the configuration I should do?

arozendojr