You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/flow-control.md
+62-3Lines changed: 62 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -303,6 +303,9 @@ to get a mapping of UIDs to names for both FlowSchemas and
303
303
PriorityLevelConfigurations.
304
304
305
305
## Observability
306
+
307
+
### Metrics
308
+
306
309
When you enable the API Priority and Fairness feature, the kube-apiserver
307
310
exports additional metrics. Monitoring these can help you determine whether your
308
311
configuration is inappropriately throttling important traffic, or find
@@ -365,9 +368,65 @@ poorly-behaved workloads that may be harming system health.
365
368
long requests took to actually execute, grouped by the FlowSchema that matched the
366
369
request and the PriorityLevel to which it was assigned.
367
370
368
-
369
-
370
-
371
+
### Debug endpoints
372
+
373
+
When you enable the API Priority and Fairness feature, the kube-apiserver serves the following additional paths at its HTTP[S] ports.
374
+
375
+
-`/debug/api_priority_and_fairness/dump_priority_levels` - a listing of all the priority levels and the current state of each. You can fetch like this:
376
+
```shell
377
+
kubectl get --raw /debug/api_priority_and_fairness/dump_priority_levels
0 commit comments