From acbb7aa2c467957684d1dae90009c24bf861b957 Mon Sep 17 00:00:00 2001 From: Cria Hu Date: Fri, 28 Feb 2020 12:53:35 +0800 Subject: [PATCH] fix broken link : https://github.com/kubernetes/community/blob/master/contributors/devel/instrumentation.md --- keps/sig-instrumentation/0034-distributed-tracing-kep.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/keps/sig-instrumentation/0034-distributed-tracing-kep.md b/keps/sig-instrumentation/0034-distributed-tracing-kep.md index 16be1808d94..9752cc23d76 100644 --- a/keps/sig-instrumentation/0034-distributed-tracing-kep.md +++ b/keps/sig-instrumentation/0034-distributed-tracing-kep.md @@ -199,7 +199,7 @@ While adding tracing to Pods is a good first step to demonstrate the viability o #### Tracing best-practices documentation -This KEP introduces a new form of instrumentation to Kubernetes, which necessitates the creation of guidelines for adding effective, standardized traces to Kubernetes components, [similar to what is found here for metrics](https://github.com/kubernetes/community/blob/master/contributors/devel/instrumentation.md). +This KEP introduces a new form of instrumentation to Kubernetes, which necessitates the creation of guidelines for adding effective, standardized traces to Kubernetes components, [similar to what is found here for metrics](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/instrumentation.md). This documentation will put forward standards for: