go/opentelemetry-go
go/opentelemetry-go
1
0
Fork 0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2024-12-14 10:13:10 +02:00
Code Issues Releases Activity
bc9cb5e354
opentelemetry-go/example/zipkin/go.mod

16 lines
370 B
Modula-2
Raw Normal View History

Fix zipkin example module name (#1308) Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
2020-11-05 17:55:25 +02:00
module go.opentelemetry.io/otel/example/zipkin
Zipkin exporter (#495) * Add zipkin exporter The zipkin exporter implements the SpanBatcher interface. It follows the current-at-the-time-of-writing document about conversion from OpenTelemetry span data to Zipkin spans. Which means that endpoint information is not yet filled. * Fix typo in docs * Add a zipkin example This sends span information to a locally running zipkin collector. Currently I have a problem getting the collector to show me the spans after accepting them with HTTP 202. Not sure if this is because of missing endpoint information. * Make gitignore consistent The fixed paths should be prefixed with a slash. The "relative" paths mean that git will ignore all the files that end with the path. * Add tests for zipkin exporter
2020-03-11 23:49:02 +02:00
Make the SDK into its own Go module (#985) * 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
2020-07-30 00:54:26 +02:00
go 1.14
Zipkin exporter (#495) * Add zipkin exporter The zipkin exporter implements the SpanBatcher interface. It follows the current-at-the-time-of-writing document about conversion from OpenTelemetry span data to Zipkin spans. Which means that endpoint information is not yet filled. * Fix typo in docs * Add a zipkin example This sends span information to a locally running zipkin collector. Currently I have a problem getting the collector to show me the spans after accepting them with HTTP 202. Not sure if this is because of missing endpoint information. * Make gitignore consistent The fixed paths should be prefixed with a slash. The "relative" paths mean that git will ignore all the files that end with the path. * Add tests for zipkin exporter
2020-03-11 23:49:02 +02:00
replace (
go.opentelemetry.io/otel => ../..
go.opentelemetry.io/otel/exporters/trace/zipkin => ../../exporters/trace/zipkin
Make the SDK into its own Go module (#985) * 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
2020-07-30 00:54:26 +02:00
go.opentelemetry.io/otel/sdk => ../../sdk
Zipkin exporter (#495) * Add zipkin exporter The zipkin exporter implements the SpanBatcher interface. It follows the current-at-the-time-of-writing document about conversion from OpenTelemetry span data to Zipkin spans. Which means that endpoint information is not yet filled. * Fix typo in docs * Add a zipkin example This sends span information to a locally running zipkin collector. Currently I have a problem getting the collector to show me the spans after accepting them with HTTP 202. Not sure if this is because of missing endpoint information. * Make gitignore consistent The fixed paths should be prefixed with a slash. The "relative" paths mean that git will ignore all the files that end with the path. * Add tests for zipkin exporter
2020-03-11 23:49:02 +02:00
)
require (
Release v0.15.0 (#1392)
2020-12-11 07:00:59 +02:00
go.opentelemetry.io/otel v0.15.0
go.opentelemetry.io/otel/exporters/trace/zipkin v0.15.0
go.opentelemetry.io/otel/sdk v0.15.0
Zipkin exporter (#495) * Add zipkin exporter The zipkin exporter implements the SpanBatcher interface. It follows the current-at-the-time-of-writing document about conversion from OpenTelemetry span data to Zipkin spans. Which means that endpoint information is not yet filled. * Fix typo in docs * Add a zipkin example This sends span information to a locally running zipkin collector. Currently I have a problem getting the collector to show me the spans after accepting them with HTTP 202. Not sure if this is because of missing endpoint information. * Make gitignore consistent The fixed paths should be prefixed with a slash. The "relative" paths mean that git will ignore all the files that end with the path. * Add tests for zipkin exporter
2020-03-11 23:49:02 +02:00
)
Reference in New Issue Copy Permalink