1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2024-12-04 09:43:23 +02:00
opentelemetry-go/example
Tyler Yahn 07d5f77749
Rename plugin directory to instrumentation (#779)
* Rename plugin directory to instrumentation

As per https://github.com/open-telemetry/opentelemetry-specification/pull/539

* Update package paths

* Fix tracer names in othttp instrumentation
2020-05-30 14:53:32 -07:00
..
basic Merge branch 'master' into pre_release_v0.6.0 2020-05-21 15:45:47 -07:00
grpc Rename plugin directory to instrumentation (#779) 2020-05-30 14:53:32 -07:00
http Rename plugin directory to instrumentation (#779) 2020-05-30 14:53:32 -07:00
jaeger Prepare for releasing v0.6.0 2020-05-21 12:10:12 -07:00
namedtracer Prepare for releasing v0.6.0 2020-05-21 12:10:12 -07:00
otel-collector Prepare for releasing v0.6.0 2020-05-21 12:10:12 -07:00
prometheus Merge branch 'master' into pre_release_v0.6.0 2020-05-21 15:45:47 -07:00
zipkin Prepare for releasing v0.6.0 2020-05-21 12:10:12 -07:00
README.md Namespace import path under "/otel" (#274) 2019-11-01 11:40:29 -07: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.