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

Part one: • OpenTelemetry & Python...
Part two: • OpenTelemetry & Python...
All the code is here: github.com/agardnerIT/python-...
00:00 Intro and Recap
00:27 Starting Jaeger
01:12 Explanation: Why you should use an OpenTelemetry Collector
01:40 Starting the OpenTelemetry Collector
01:43 Testing Span Ingestion using tracepusher
02:23 View the test span in Jaeger
02:46 New additions to requirements.txt
03:00 Python code runthrough
03:10 Sending spans to the gRPC Collector endpoint
03:56 Run the application to send traces to Jaeger
04:11 View the app span in Jaeger
04:46 Span Attributes for Feature Flags
05:05 Feature flags you need to know for operations
05:22 Feature flag code explained
05:52 Toggling the flag off
06:03 View new span in Jaeger
06:11 Why the disparity in span time?
06:21 View Span Attributes on trace
06:50 The answer: why spans are different
07:00 Other Span Attribute possibilities
07:40 Summary: Spans from Python to Jaeger via Collector
07:58 Deep Dive: OTLP Format
08:40 Deep Dive: The Architecture
10:00 Deep Dive: GRPC vs. HTTP
10:19 HTTP Diagram
10:43 GRPC Diagram
11:01 OpenTelemetry Port Standards: HTTP and GRPC
11:49 Summary
12:13 Preview of the next video

[@Emma-tm1mx]

wow thanks subscribed

[@agardnerit]

Thanks for the sub!

[@akshayawate7239]

Thanks. Waiting for sampling vids

[@agardnerit]

Great idea!

[@akshayawate7239]

Any specific reason to use 6004 port instead of 4317. ?

[@agardnerit]

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