1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2024-12-14 10:13:10 +02:00
opentelemetry-go/example
Tyler Yahn 799c178925
Make opentracing bridge into own Go module (#1038)
* Make opentracing bridge into own Go module

* Update dependabot config

* Clean dependencies of project

Now the bridge is a module, clean all upstream modules that no longer
implicitly depend on it.

* Update Changelog

* go mod tidy
2020-08-06 07:59:41 -07:00
..
basic Make opentracing bridge into own Go module (#1038) 2020-08-06 07:59:41 -07:00
jaeger Make opentracing bridge into own Go module (#1038) 2020-08-06 07:59:41 -07:00
namedtracer Make opentracing bridge into own Go module (#1038) 2020-08-06 07:59:41 -07:00
otel-collector Make opentracing bridge into own Go module (#1038) 2020-08-06 07:59:41 -07:00
prometheus Make opentracing bridge into own Go module (#1038) 2020-08-06 07:59:41 -07:00
zipkin Make opentracing bridge into own Go module (#1038) 2020-08-06 07:59:41 -07:00
README.md Split OTLP README to own directory 2020-06-01 13:27:23 -05:00

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.