We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the opentelemetry documentation you have link to, there is a configuration of the protocol for traces to send: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.7.0/specification/protocol/exporter.md#specify-protocol. It can be grpc or http/protobuf etc.
grpc
http/protobuf
As far as I see in the code: https://github.com/caddyserver/caddy/blob/master/modules/caddyhttp/tracing/tracer.go#L61 you have only grpc supported.
It would be great to have other options like http/protobuf supported as well. Some tracing ingesters have the no GRPC support by different reasons.
The text was updated successfully, but these errors were encountered:
PRs welcome. Most maintainers don't use tracing or metrics ourselves, so we need to lean on the community to contribute improvements.
Sorry, something went wrong.
No branches or pull requests
In the opentelemetry documentation you have link to, there is a configuration of the protocol for traces to send: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.7.0/specification/protocol/exporter.md#specify-protocol. It can be
grpc
orhttp/protobuf
etc.As far as I see in the code: https://github.com/caddyserver/caddy/blob/master/modules/caddyhttp/tracing/tracer.go#L61 you have only
grpc
supported.It would be great to have other options like
http/protobuf
supported as well. Some tracing ingesters have the no GRPC support by different reasons.The text was updated successfully, but these errors were encountered: