mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2024-12-10 09:50:58 +02:00
8fbaa9d432
* Remove otel/sdk dependency from grpctrace Use otel/trace/testtrace instead and cleanup testing code. * Update httptrace to not depend on the SDK Update testing to use api/trace/testtrace instead. * Add changes to Changelog * Make the SDK its own Go module * Upgrade go.mod to 1.14 project wide * go mod tidy |
||
---|---|---|
.. | ||
basic | ||
grpc | ||
http | ||
jaeger | ||
namedtracer | ||
otel-collector | ||
prometheus | ||
zipkin | ||
README.md |
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.