When looking on how services usually handle variations of paths, we can see big differences between different frameworks and service implementations, which is not reflected in the API specification but has a negative impact on predictability of the behavior of an API and the way how it is or can be used. The keyword here is request path normalization, i.e.
When you have 2 HorizontalPodAutoscalers using annotations to specify the prometheus server (e.g. metric-config.external.prometheus-query.prometheus/prometheus-server: http://my-prometheus), metrics should be read from the prometheus server in the annotation.
Actual Behavior
The prometheus-server defined in the kube-metrics-server flags is used instead of using t
Kafka consumer lag-checking application for monitoring, written in Scala and Akka HTTP; a wrap around the Kafka consumer group command. Integrations with Cloudwatch and Datadog. Authentication recently added
When looking on how services usually handle variations of paths, we can see big differences between different frameworks and service implementations, which is not reflected in the API specification but has a negative impact on predictability of the behavior of an API and the way how it is or can be used. The keyword here is request path normalization, i.e.