Better understand your APIs through traffic
summary
Live demo shows Mizu (download from getmizu.io) deployed as kubectl daemonsets to capture Kubernetes, Kafka and Redis traffic on a laptop, apply real-time rules and catch SLO breaches — e.g., a catalog endpoint set to 20 ms returns 68 ms and filters reveal all >5 ms requests. Captured payloads expose accidental PII, allow schema validation, generate a service map and creates OpenAPI/AsyncAPI specs for sharing, and cleans up on Ctrl+C so nothing is left in cluster.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:30Agenda
- 1:53Track Sensitive Data
- 2:28Api Traffic Visibility
- 4:03Local versus Remote
- 6:16Debugging
- 13:25Zombie and Ghost Apis
- 15:50Getmizu
- 17:53How To Filter the Traffic
- 18:31Schema Validations
- 22:17How Do I Get the Documentation on the Service Map
related talks
56mObservability in Action for your Service Mesh
36mWhat's going on in my cluster?
24mObservability in the MLOps Lifecycle with Prometheus
40mA hitchhikers guide to observe (Java) applications in Kubernetes
29mKubernetes-Defined Monitoring [I]
45mFrom k9s to OpenTelemetry: A guide to observability for your apps in K8s
28mImprove Monitoring and Observability for Kubernetes with OSS Tools
12mThe Road Ahead: Istio Observability