mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2025-01-05 22:54:18 +02:00
d8682c1999
* Create MeterImpl interface * Checkpoint w/ sdk.go building * Checkpoint working on global * api/global builds (test fails) * Test fix * All tests pass * Comments * Add two tests * Comments and uncomment tests * Precommit part 1 * Still working on tests * Lint * Add a test and a TODO * Cleanup * Lint * Interface()->Implementation() * Apply some feedback * From feedback * (A)Synchronous -> (A)Sync * Add a missing comment * Apply suggestions from code review Co-Authored-By: Krzesimir Nowak <qdlacz@gmail.com> * Rename a variable Co-authored-by: Krzesimir Nowak <qdlacz@gmail.com> |
||
|---|---|---|
| .. | ||
| basic | ||
| grpc | ||
| http | ||
| jaeger | ||
| namedtracer | ||
| 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.