mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2024-12-10 09:50:58 +02:00
3b01a854d1
* Make the stdout exporter its own package Follow the pattern of the other exporters. * Update dependabot with stdout exporter * Add replace directives for stdout exporter * Remove outdated example test from metric SDK * go mod tidy * Update othttp example test Remove unused stdout exporter. * Remove tests in API that depend on stdout exporter The global package does not need to be validated with the SDK. A more properly constructed end-to-end integration test should be built if this is actually needed. * Add replace clause for otel in stdout go.mod |
||
|---|---|---|
| .. | ||
| 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.