Dealing with the Pesky Path Parameter Problem: Service Profiles
For platform owners and developers to truly grok their service behaviors in Kubernetes, they must understand their services in terms of actual request and responses by HTTP path. Unfortunately, a near …
Talk Title | Dealing with the Pesky Path Parameter Problem: Service Profiles |
Speakers | Alex Leong (Software Engineer, Buoyant) |
Conference | KubeCon + CloudNativeCon Europe |
Conf Tag | |
Location | Barcelona, Spain |
Date | May 19-23, 2019 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
For platform owners and developers to truly grok their service behaviors in Kubernetes, they must understand their services in terms of actual request and responses by HTTP path. Unfortunately, a nearly unlimited number of unique potential paths tends to overwhelm time series capture, making it difficult to get a clear picture of service behaviors. In this talk I’ll introduce the concept of the Service Profile, a custom Kubernetes resource used by Linkerd. The service profile lets operators define permitted routes for the service with regular expressions, which allows Prometheus to scrape and aggregate service behaviors in a manageable way. It also allows operators to set detailed service behavior rules such as retries and timeouts that can be easily reproduced and monitored.