You MUST Instrument Your Code With OpenTelemetry (OTEL)!

If we want to gain insights into application behavior, we MUST instrument our code. However, instrumenting code can take time and effort and so we better do it in a way that avoids being locked into any specific tool. That's where Open Telemetry comes in with its instrumentation standard, independent of the tools where logs, metrics, and traces are collected.

#opentelemetry #instrumentation #traces #metrics #logsesports

▬▬▬▬▬▬ 😳 Sponsor 😳 ▬▬▬▬▬▬
🔗 Robusta: https://robusta.dev

Consider joining the channel:    / devopstoolkit  

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬
➡ Gist with the commands: https://gist.github.com/38b4b02bef304...
🔗 OpenTelemetry: https://opentelemetry.io
🎬 Kubernetes Notifications, Troubleshooting, And Automation With Robusta:    • Kubernetes Notifications, Troubleshoo...  

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬
If you are interested in sponsoring this channel, please use https://calendly.com/vfarcic/meet to book a timeslot that suits you, and we'll go over the details. Or feel free to contact me over Twitter or LinkedIn (see below).

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬
➡ Twitter:   / vfarcic  
➡ LinkedIn:   / viktorfarcic  

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬
🎤 Podcast: https://www.devopsparadox.com/
💬 Live streams:    / devopsparadox  

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction To OpenTelemetry
02:42 What Is Instrumentation And Why Do We Need It?
03:26 Robusta (sponsor)
04:08 What Is Instrumentation And Why Do We Need It? (cont.)
09:09 What Is OpenTelemetry And Why Do We Need It?
15:47 Should You Instrument Your Applications With OpenTelemetry?