From 00d9ada416c0055c7e9e673df6aa2c698364d3dd Mon Sep 17 00:00:00 2001 From: houjun Date: Fri, 12 Jul 2019 23:25:05 +0800 Subject: [PATCH] Fix error link (#15388) --- .../extend-kubernetes/compute-storage-net/device-plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md index 749d1adfce..26f48b79e0 100644 --- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md +++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md @@ -142,7 +142,7 @@ In order to monitor resources provided by device plugins, monitoring agents need discover the set of devices that are in-use on the node and obtain metadata to describe which container the metric should be associated with. Prometheus metrics exposed by device monitoring agents should follow the -[Kubernetes Instrumentation Guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/instrumentation.md), +[Kubernetes Instrumentation Guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/instrumentation.md), which requires identifying containers using `pod`, `namespace`, and `container` prometheus labels. The kubelet provides a gRPC service to enable discovery of in-use devices, and to provide metadata for these devices: