Multi-tenant Logging with Opentelemetry Collector
summary
Builds a Kubernetes operator called Telemetry Controller that models logs as collector/tenant/subscription/output CRs, deploys OpenTelemetry Collector as a DaemonSet per node, and demonstrates parsed nginx logs landing in OpenObserve. Implements tenant selectors, OTL-based subscriptions, and outputs that set tenant headers; first scenario (aggregator per-tenant) is working in demo, cross-tenant shared-output support is in progress. Claims reduce bandwidth and noisy-neighbor failures; shows a 10 TB/day example costing ~$30k/month in egress.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Kubernetes logging challenges
- 4:17OpenTelemetry protocol benefits
- 10:17Multi-tenancy in logging
- 15:55Traditional logging problems
- 17:21Telemetry Controller intro
- 21:01Live demo setup
- 23:15Custom resources
- 26:08Tenant subscriptions
- 28:16Output config
- 31:07Controller purpose
- 32:34Demo log aggregation
- 35:04Future log sources
- 36:31Monitoring pipeline
- 38:16Q&A
related talks
40mMulti-tenant Logging with Opentelemetry Collector
26mTurn the Volume Down on Noisy Neighbors!
34mKubernetes Observability with OpenTelemetry
32mDesign Observability Solution for Multi-Tenancy Environment
13mManaging Observability Data at the Edge with the OpenTelemetry Collector and OTTL
37mObservability For You And Me With Opentelemetry
55mCloud-Native Observability with OpenTelemetry
01h 03mGet a Grip on your Telemetry using the OpenTelemetry Collector