1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2025-12-03 23:21:27 +02:00
Files
opentelemetry-go/example/zipkin
Tigran Najaryan e72a235518 Add ability to parse Schema files according to OTEP 0152 (#2267)
* Add ability to parse Schema files according to OTEP 0152

The parser and parsed representation (AST) are placed in a separate
Go module so that they are can be consumed independently without
the need to bring the rest of the SDK.

Ability to use the parsed representation for schema conversions
can be added later.

* Fixes based on PR comments

* Rename "label" to "attributes"

See https://github.com/open-telemetry/oteps/pull/181

* Fixes based on PR comments

* Add README.md

* Wrap the error in Parse()

* Add docs for exporter types

* Use yaml.NewDecoder

* Verify parsed content in the test

* Fix indentation in README example

* Fix README spaces vs tabs

* Correctly space imports

* Add heading to README

Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
2021-10-15 09:44:13 -07:00
..

Zipkin Exporter Example

Send an example span to a Zipkin service. These instructions expect you have docker-compose installed.

Bring up the zipkin-collector service and example zipkin-client service to send an example trace:

docker-compose up --detach zipkin-collector zipkin-client

The zipkin-client service sends just one trace and exits. Retrieve the traceId generated by the zipkin-client service; should be the last line in the logs:

docker-compose logs --tail=1 zipkin-client

With the traceId you can view the trace from the zipkin-collector service UI hosted on port 9411, e.g. with traceId of f5695ba3b2ed00ea583fa4fa0badbeef: http://localhost:9411/zipkin/traces/f5695ba3b2ed00ea583fa4fa0badbeef

Shut down the services when you are finished with the example:

docker-compose down