Automatic logs, traces and metrics in K8s using OpenTelemetry & SigNoz
summary
Demo shows auto-instrumentation via OpenTelemetry Operator on Kubernetes: install operator, create a sidecar collector and an instrumentation CRD, add two annotations, and a Spring Petclinic app starts emitting traces, metrics and logs visible in SigNoz in about five minutes. Traces point to an SQL call as the latency culprit and related logs can be filtered by trace ID. Backend uses OTel collector + ClickHouse and the project ecosystem reports ~12k GitHub stars, 2.6k Slack members, 100+ contributors.
AI-written summary · about
chapters (13)
- 0:00Observability with OpenTelemetry
- 1:26Observability in production
- 3:53SigNoz open-source platform
- 5:00Metrics traces and logs
- 7:49Correlating signals for troubleshooting
- 11:09OpenTelemetry instrumentation standard
- 14:17Automating observability in K8s
- 15:50Demo setup with OpenTelemetry operator
- 20:29Deploying Java application
- 22:21Viewing signals in SigNoz
- 23:47Unified observability benefits
- 24:09Summary
- 25:11Q&A
related talks
23mOpenTelemetry Auto Instrumentation for Effortless Observability
34mKubernetes Observability with OpenTelemetry
45mFrom Noise To Signal: Building Smart Observability Pipelines With OpenTelemetry
28mImplementing Observability in Kubernetes
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
50mBootiful OpenTelemetry
50mGuide to Observability with OpenTelemetry
45mFrom k9s to OpenTelemetry: A guide to observability for your apps in K8s