diff options
author | Andrew Gerrand <adg@golang.org> | 2016-10-05 08:12:01 +1100 |
---|---|---|
committer | Andrew Gerrand <adg@golang.org> | 2016-10-04 21:21:03 +0000 |
commit | 41f3680fc788488fdecbe2e652604680a90dc2a8 (patch) | |
tree | 38c35e40063826877e313799892d1ab7ec4643b0 | |
parent | fb4799a1b541e8a91360905e965f94641e553610 (diff) |
content: fix more links in tracing blog post
Change-Id: I2aec5e9b4f4daec15f724f386eb57bbd34fba6f6
Reviewed-on: https://go-review.googlesource.com/30331
Reviewed-by: Andrew Gerrand <adg@golang.org>
-rw-r--r-- | content/http-tracing.article | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/content/http-tracing.article b/content/http-tracing.article index 0e586c5..d006bf6 100644 --- a/content/http-tracing.article +++ b/content/http-tracing.article @@ -8,7 +8,7 @@ Jaana Burcu Dogan In Go 1.7 we introduced HTTP tracing, a facility to gather fine-grained information throughout the lifecycle of an HTTP client request. -Support for HTTP tracing is provided by the [[`net/http/httptrace`][https://golang.org/pkg/net/http/httptrace/]] +Support for HTTP tracing is provided by the [[https://golang.org/pkg/net/http/httptrace/][`net/http/httptrace`]] package. The collected information can be used for debugging latency issues, service monitoring, writing adaptive systems, and more. @@ -26,9 +26,9 @@ during an HTTP round trip about a variety of events. These events include: * Tracing events You can enable HTTP tracing by putting an -[[`*httptrace.ClientTrace`][https://golang.org/pkg/net/http/httptrace/#ClientTrace]] -containing hook functions into a request's [[`context.Context`][https://golang.org/pkg/context/#Context]]. -Various [[`http.RoundTripper`][https://golang.org/pkg/net/http/#RoundTripper]] +[[https://golang.org/pkg/net/http/httptrace/#ClientTrace][`*httptrace.ClientTrace`]] +containing hook functions into a request's [[https://golang.org/pkg/context/#Context][`context.Context`]]. +Various [[https://golang.org/pkg/net/http/#RoundTripper][`http.RoundTripper`]] implementations report the internal events by looking for context's `*httptrace.ClientTrace` and calling the relevant hook functions. |