1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2024-12-10 09:50:58 +02:00
opentelemetry-go/example
ET bd1e174e60
Add "peer.service" semantic to standard attributes (#898)
Co-authored-by: Liz Fong-Jones <lizf@honeycomb.io>
2020-07-06 11:36:49 -04:00
..
basic Update opentracing dependency (#885) 2020-07-01 17:51:06 -04:00
grpc Update opentracing dependency (#885) 2020-07-01 17:51:06 -04:00
http Add "peer.service" semantic to standard attributes (#898) 2020-07-06 11:36:49 -04:00
jaeger Update opentracing dependency (#885) 2020-07-01 17:51:06 -04:00
namedtracer Update opentracing dependency (#885) 2020-07-01 17:51:06 -04:00
otel-collector Update opentracing dependency (#885) 2020-07-01 17:51:06 -04:00
prometheus Update opentracing dependency (#885) 2020-07-01 17:51:06 -04:00
zipkin Update opentracing dependency (#885) 2020-07-01 17:51:06 -04: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.