From fae60fa146b67e7fb1052027fd5a3118b85a8871 Mon Sep 17 00:00:00 2001 From: whitewindmills Date: Thu, 3 Aug 2023 14:13:17 +0800 Subject: [PATCH] update policy preemption proposals Signed-off-by: whitewindmills --- docs/proposals/scheduling/policy-preemption/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/proposals/scheduling/policy-preemption/README.md b/docs/proposals/scheduling/policy-preemption/README.md index 7c0d1b087..978d541f1 100644 --- a/docs/proposals/scheduling/policy-preemption/README.md +++ b/docs/proposals/scheduling/policy-preemption/README.md @@ -306,7 +306,7 @@ Also, we need to add a preemption logic. The overall process is shown in the pic For each preemption operation, the component needs to have a corresponding metrics record. For metrics, we will record the total number of times a resource template is preempted. And we will use events to reflect the details of each preemption operation. -For example, preemption_counts_total{namespace=default, name=nginx} 4. +For example, policy_preemption_total{result=success} 4. #### karmada-webhook