Turn the Volume Down on Noisy Neighbors!
Talkat Observability Day North America 2024 · on Tuesday, 2024-11-12· at 15:20· Salt Palace | Level 2 | 255 B·
summary
A Kubernetes operator called Telemetry Controller runs on top of the OpenTelemetry Collector to turn telemetry into native k8s resources: Collector CRs with tenant selectors, Tenant CRs, Subscriptions and Outputs. It isolates receivers per tenant to avoid cluster-wide backpressure, routes logs by parsed attributes (demo uses a regex to extract request host), and adds a bridge resource to forward only matching ingress logs into tenant spaces. A resource-reuse bug in OTel Collector appears during demo; tenant metrics and per-subscription monitoring work.
AI-written summary · about
chapters (10)
- 0:00Observability in Kubernetes
- 3:34Multi-tenancy challenges
- 6:24Telemetry Controller intro
- 8:10Telemetry Controller workflow
- 11:20Single-tenant logging demo
- 14:15Multi-tenant logging config
- 16:24Tenant access logs
- 20:30Routing logs with Bridge
- 21:33OpenTelemetry bug
- 22:39Q&A
related talks
40mMulti-tenant Logging with Opentelemetry Collector- 40mMulti-tenant Logging with Opentelemetry Collector
34mKubernetes Observability with OpenTelemetry
01h 03mGet a Grip on your Telemetry using the OpenTelemetry Collector
28mControlling data overhead from the OpenTelmetry Collector
25mOpenTelemetry Collector Deployment Patterns
28mImplementing Observability in Kubernetes
47mWhat Is This OpenTelemetry Thing?