Open wojtek-t opened 2 years ago
I believe the easiest way is to add new prometheus query to GenericPrometheusQuery here: https://github.com/kubernetes/perf-tests/blob/1f00a7787f9f47bad251d4e791a0117ad6fe7e1d/clusterloader2/testing/load/modules/measurements.yaml#L122 instead of creating new measurement.
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/assign
The only missing thing now is to enable the new measurement in our tests, right?
Enabling measurement and then based on results possibly adding alerting to it.
One of the important metrics that may suggest overload of the control plane is the number of watches that are closed by kube-apiserver because they don't keep up (or watchcache itself is not keeping). We want to add a check to our tests that will be validating if this metrics is not too high.
Metrics to exercise:
The easiest way to do it is probably add to prometheus-based measurement, but @marseel to confirm.