OpenTelemetry and Python: Sending spans from Python to Jaeger via an OpenTelemetry Collector

  Рет қаралды 1,274

Adam Gardner

Adam Gardner

Күн бұрын

Пікірлер: 19
@zuowang5185
@zuowang5185 2 ай бұрын
did you confuse http vs grpc with tcp vs websocket? I thought grpc is where you define the schema for compact serialization and unmarshaling
@vivekshukla2480
@vivekshukla2480 4 ай бұрын
Thank you so much. How can I start the collector up? Your code in github doesn't have `otelcol` file - I would appreciate your help.
@agardnerit
@agardnerit 4 ай бұрын
I don’t add (and don’t recommend adding) large binaries to repos as it bloats the repo unnecessarily. There are many collector distributions available to choose from (that’s my next video about how you choose). But to get you going for now: download the appropriate binary from here: github.com/open-telemetry/opentelemetry-collector-releases/latest extract it and run it
@vivekshukla2480
@vivekshukla2480 4 ай бұрын
What do I need to get `./otelcol --config=collector-config.yaml` running, in your previous videos I have not seen you install any specific tool to be able to call this command successfully, Did I miss something?
@agardnerit
@agardnerit 4 ай бұрын
Thanks. You're right actually. I missed that. I'll make a quick video explaining the different options soon. But in short, see this page: opentelemetry.io/docs/collector/installation/ There are many different distributions of the collector, the OTEL project produces a few that supposedly are optimised for particular use cases. Some vendors produce their own and you can even build your own. In these videos I use the contributors distribution. I downloaded the binary for my OS from here: github.com/open-telemetry/opentelemetry-collector-releases/releases/latest
@vivekshukla2480
@vivekshukla2480 4 ай бұрын
@@agardnerit Thank you for your quick response. I will let you know how it goes, to provide some background, I was able to follow your kzbin.info/www/bejne/a3jHiJyuqNSjm8ksi=GIkjN1HisC-gSE6y video that let me visualize the traces. I am assuming this video will take it a step further. Am I not right?
@leamon9024
@leamon9024 4 ай бұрын
Hi, thanks for the video. Could you explain the difference between OpenTelemetry Collector and jaeger-collector?
@agardnerit
@agardnerit 4 ай бұрын
Thanks for the suggestion, I'll put this topic on my backlog! The timing of your request is interesting as the Jaeger project is looking to move more towards the OTEL Collector. IMO using the OTEL collector is the future proof decision.
@akshayawate7239
@akshayawate7239 7 ай бұрын
Any specific reason to use 6004 port instead of 4317. ?
@agardnerit
@agardnerit 7 ай бұрын
I tried to make that clear in the video. Obviously I didn’t do a good job! Jaeger all-in-one image comes with its own collector so 4317 was already in use. It was also to demonstrate that even though 4317 is the standard, you don’t HAVE to use that
@vivekshukla2480
@vivekshukla2480 4 ай бұрын
My response somehow got deleted, but this video I am having trouble following, for example - starting from using the docker command to run the jaeger, so I used previous video to run the jaeger then even after jumping through hoops I could never get past the issue when I run `python app.py` command. I receive Transient error StatusCode.UNAVAILABLE encountered while exporting traces to 127.0.0.1:6004. error. Suggestion is appreciated.
@agardnerit
@agardnerit 4 ай бұрын
You need to run Jaeger AND a seperate standalone Otel collector. It’s the standalone collector that you need to configure (via the YAML file) to listen on 6004. This is because jaeger already runs a collector on 4317 / 4318 so you can’t use those ports for your standalone.
@akshayawate7239
@akshayawate7239 7 ай бұрын
Thanks. Waiting for sampling vids
@agardnerit
@agardnerit 7 ай бұрын
Great idea!
@vivekshukla2480
@vivekshukla2480 4 ай бұрын
Running this `docker run -p 16686:16686 -p 4317:4317 225` produces error stating Unable to find image `225:latest` locally. I was so looking forward to getting this done, using your tutorials, but I may end up moving on to someone else's. :(
@agardnerit
@agardnerit 4 ай бұрын
That command is referencing an existing container ID because I had Jaeger running previously. Just replace 255 with jaegertracing/all-in-one:1.60 www.jaegertracing.io/docs/1.60/getting-started/
@vivekshukla2480
@vivekshukla2480 4 ай бұрын
@@agardnerit Thank you so much. How can I start the collector up? Your code in github doesn't have otelcol file - I would appreciate your help.
@Emma-tm1mx
@Emma-tm1mx 6 ай бұрын
wow thanks subscribed
@agardnerit
@agardnerit 6 ай бұрын
Thanks for the sub!
OpenTelemetry Collector: EVERYTHING you need to know [to get started]
10:07
VIP ACCESS
00:47
Natan por Aí
Рет қаралды 25 МЛН
Smart Sigma Kid #funny #sigma
00:33
CRAZY GREAPA
Рет қаралды 38 МЛН
Mom Hack for Cooking Solo with a Little One! 🍳👶
00:15
5-Minute Crafts HOUSE
Рет қаралды 22 МЛН
Try this prank with your friends 😂 @karina-kola
00:18
Andrey Grechka
Рет қаралды 4,6 МЛН
COMPLETE No-Nonsense VSCode Setup for Python Devs
26:05
ArjanCodes
Рет қаралды 44 М.
Spans vs. Traces in OpenTelemetry: Which is Which?
3:52
Adam Gardner
Рет қаралды 839
OpenTelemetry: Simplifying Hybrid Cloud Monitoring
5:40
IBM Technology
Рет қаралды 6 М.
What is OpenTelemetry? - Explanation and Demo
24:54
Better Stack
Рет қаралды 2,2 М.
OpenTelemetry Instrumented FastAPI
6:50
Adam Gardner
Рет қаралды 12 М.
Distributed Tracing With Jaeger And OpenTelemetry In Kubernetes
18:58
DevOps Toolkit
Рет қаралды 30 М.
Which OpenTelemetry Collector Distribution?
6:25
Adam Gardner
Рет қаралды 569
VIP ACCESS
00:47
Natan por Aí
Рет қаралды 25 МЛН