Seeing Is Believing: OpenTelemetry and OpenSearch in Next-Gen Observability
summary
OpenTelemetry provides SDKs and an optional collector (sidecar / daemonset / standalone) to auto- or manually instrument apps, perform sampling/filtering, and export traces, metrics and logs to multiple backends. OpenSearch ingests time-series metrics and high-volume logs using time-based indexing, sharding, replication and rollups for long retention and low cost. The demo shows a Robot Shop request traced across six calls with correlated error logs and a 3D dependency graph correlating traces, metrics and logs so issues are found and linked.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:42What is OpenTelemetry and its core concepts
- 2:28OpenTelemetry growth
- 3:51OpenTelemetry benefits
- 4:36Telemetry data pillars
- 7:48OpenTelemetry components
- 8:54OpenTelemetry Collector role
- 10:15Telemetry data in backends
- 13:05OpenSearch in observability
- 16:13Dependency visualization demo
- 19:01Q&A
related talks
34mHow to Do Microservice Observability with OpenSearch
22mFrom Telemetry to Insight: Building AI-Powered Observability Pipelines with OpenSearch
50mGuide to Observability with OpenTelemetry
29mOpenTelemetry With OpenSearch: Use-Cases, Status and Roadmap
11mOpenTelemetry + OpenSearch Integration
06mSponsored Keynote: OpenSearch - See Everything: Open Observability for Agentic AI
37mBuilding Modern Observability Architecture With OpenSearch, OS Ingest...
06mWhy OpenSearch?