From b66a80db00435d8d56734aadc63aef1cd2db8d64 Mon Sep 17 00:00:00 2001 From: "xin.li" Date: Fri, 29 Apr 2022 18:43:27 +0800 Subject: [PATCH] [zh] modify debug link in resource-metrics-pipeline.md Signed-off-by: xin.li --- .../docs/tasks/debug/debug-cluster/resource-metrics-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/debug/debug-cluster/resource-metrics-pipeline.md b/content/en/docs/tasks/debug/debug-cluster/resource-metrics-pipeline.md index ce74c03fb6..62bcc6dfba 100644 --- a/content/en/docs/tasks/debug/debug-cluster/resource-metrics-pipeline.md +++ b/content/en/docs/tasks/debug/debug-cluster/resource-metrics-pipeline.md @@ -28,7 +28,7 @@ The Metrics API, and the metrics pipeline that it enables, only offers the minim CPU and memory metrics to enable automatic scaling using HPA and / or VPA. If you would like to provide a more complete set of metrics, you can complement the simpler Metrics API by deploying a second -[metrics pipeline](/docs/tasks/debug-application-cluster/resource-usage-monitoring/#full-metrics-pipeline) +[metrics pipeline](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/#full-metrics-pipeline) that uses the _Custom Metrics API_. {{< /note >}}