Dealing with the Pesky Path Parameter Problem: Service Profiles
summary
Prometheus metrics explode when path labels come from unsanitized requests, so the solution is a Kubernetes ServiceProfile CRD that maps paths to finite buckets using regex routes, turning arbitrary IDs into a small set of route labels for Prometheus. That lets Linkerd expose path-aware metrics without creating millions of time series (six labels with ten values each = 1,000,000), supports retries and timeouts per route, reloads profiles dynamically via watches, and can be generated from OpenAPI, protobuf or tap.
AI-written summary · about
chapters (5)
related talks
27mShow Me Your Labels and I’ll Tell You Who You Are
25mK8s Labels Everywhere! Decluttering With Node Profile Discovery.
36mIngressRoute: A Path Towards a Better Ingress Object for Kubernetes
13mConnecting Prometheus and OpenTelemetry Data for Faster Troublesho...
26mModern HTTP Routing
30mWho Let the Pods Out? Extending Kubernetes with Custom Controllers and CRDs
23mThe Legend of Config: Breath of the Cluster
33mMastering Kubernetes Operators with KubeBuilder: Sending Metrics to Prometheus