From 01688205a841faa39b5dc279ce1d99dee8e2e481 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Tue, 14 Aug 2018 16:52:46 +0200 Subject: [PATCH] Fixed wrong link --- docs/src/main/asciidoc/spring-cloud-sleuth.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/spring-cloud-sleuth.adoc b/docs/src/main/asciidoc/spring-cloud-sleuth.adoc index 6f2eab8fd..161e90819 100644 --- a/docs/src/main/asciidoc/spring-cloud-sleuth.adoc +++ b/docs/src/main/asciidoc/spring-cloud-sleuth.adoc @@ -149,7 +149,7 @@ void userCode() { ==== RPC tracing -TIP: Check for https://github.com/openzipkin/sleuth/tree/master/instrumentation[instrumentation written here] and http://zipkin.io/pages/existing_instrumentations.html[Zipkin's list] before rolling your own RPC instrumentation. +TIP: Check for https://github.com/openzipkin/brave/tree/master/instrumentation[instrumentation written here] and http://zipkin.io/pages/existing_instrumentations.html[Zipkin's list] before rolling your own RPC instrumentation. RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation.