Loading video player...
š Stop juggling multiple observability SDKs! In this video, I show you how OpenTelemetry replaces ALL vendor-specific libraries with ONE universal standard. š« DELETE these from your project: - dd-trace (Datadog) - prom-client (Prometheus) - jaeger-client (Jaeger) - newrelic (New Relic) - zipkin (Zipkin) ā REPLACE with just ONE: - @opentelemetry/sdk-node š What You'll Learn: 00:00 - The Problem with Vendor Lock-in 01:30 - What is OpenTelemetry? 03:00 - How the OTel Pipeline Works 05:00 - Code Walkthrough (Node.js/Express) 08:00 - Collector Configuration 09:30 - Live Demo: Jaeger + Prometheus + Grafana 13:00 - Switching Backends WITHOUT Code Changes š ļø Tech Stack: - Node.js / Express / TypeScript - OpenTelemetry SDK - OTel Collector - Jaeger (Distributed Tracing) - Prometheus (Metrics) - Grafana (Dashboards) š Resources: - GitHub Repo: https://github.com/tkssharma/otel-demo-nestjs - OpenTelemetry Docs: https://opentelemetry.io - CNCF Project: https://www.cncf.io/projects/opentelemetry/ š” OpenTelemetry is supported by: Datadog, New Relic, Grafana Cloud, AWS X-Ray, Azure Monitor, Google Cloud Trace, Honeycomb, Dynatrace, Splunk, Elastic APM, and 50+ more vendors! šÆ Who is this for? - Backend Developers - DevOps Engineers - SREs - Anyone tired of vendor lock-in! š Like & Subscribe for more observability content! #OpenTelemetry #Observability #DevOps #Monitoring