-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(otelx): add support for the GRPC protocol in Otel #784
base: master
Are you sure you want to change the base?
Conversation
@@ -85,22 +85,23 @@ require ( | |||
go.opentelemetry.io/contrib/propagators/b3 v1.21.0 | |||
go.opentelemetry.io/contrib/propagators/jaeger v1.21.1 | |||
go.opentelemetry.io/contrib/samplers/jaegerremote v0.15.1 | |||
go.opentelemetry.io/otel v1.21.0 | |||
go.opentelemetry.io/otel v1.26.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
required update to support GRPC.
This brought in the other dependency updates.
var client otlptrace.Client | ||
if c.Providers.OTLP.Transport == "GRPC" { | ||
client = getOTLPGRPClient(c) | ||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be required to add http/json
and http/protobuf
in the future. At the moment we default to the current behaviour
https://opentelemetry.io/docs/specs/otel/protocol/exporter/#specify-protocol
Our system cannot currently accept Otel data via
http
. As such we need support to send this using theGRPC
transport option.This PR adds a new property to allow this to be specified - with the current
http
as the default option to prevent any breaking changes.Related Issue or Design Document
Checklist
If this pull request addresses a security vulnerability,
I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
Further comments