From bb492d3fd221e11a3151990ab8495261c1d1233a Mon Sep 17 00:00:00 2001 From: Anthony Mirabella Date: Mon, 17 Aug 2020 22:59:01 -0400 Subject: [PATCH] Remove example/README.md that referenced moved HTTP example (#1066) Co-authored-by: Tyler Yahn --- example/README.md | 46 ---------------------------------------------- 1 file changed, 46 deletions(-) delete mode 100644 example/README.md diff --git a/example/README.md b/example/README.md deleted file mode 100644 index 71ec3dd20974..000000000000 --- a/example/README.md +++ /dev/null @@ -1,46 +0,0 @@ -# Example - -## HTTP -This is a simple example that demonstrates tracing http request from client to server. The example -shows key aspects of tracing such as: - -- Root Span (on Client) -- Child Span (on Client) -- Child Span from a Remote Parent (on Server) -- SpanContext Propagation (from Client to Server) -- Span Events -- Span Attributes - -Example uses -- open-telemetry SDK as trace instrumentation provider, -- httptrace plugin to facilitate tracing http request on client and server -- http trace_context propagation to propagate SpanContext on the wire. -- stdout exporter to print information about spans in the terminal - -### How to run? - -#### Prequisites - -- go 1.13 installed -- GOPATH is configured. - -#### 1 Download git repo -``` -GO111MODULE="" go get -d go.opentelemetry.io/otel -``` - -#### 2 Start Server -``` -cd $GOPATH/src/go.opentelemetry.io/otel/example/http/ -go run ./server/server.go -``` - -#### 3 Start Client -``` -cd $GOPATH/src/go.opentelemetry.io/otel/example/http/ -go run ./client/client.go -``` - -#### 4 Check traces in stdout - -The spans should be visible in stdout in the order that they were exported.