-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
JSON over HTTP REST API for Jaeger collector #1466
Comments
https://github.com/jaegertracing/jaeger/blob/master/cmd/collector/app/builder/builder_flags.go#L47 jaeger collector does have a way to submit thrift spans over http. You are correct that we do not have a JSON over HTTP endpoint in the collector. |
Thrift Spans have a dependency on Thrift library. That increases the size of the web page and lots of steps to convert thrifts to Javascript compatible format. Is there any plan to accept Jaeger spans as JSON in near future? |
Yes we do have plans to support JSON in the collector to unblock that exact issue. jaegertracing/jaeger-client-javascript#1 |
Thanks @black-adder |
HI, Is jaeger collector accepting JSON format over HTTP collector endpoint. because I am facing same issue in 2022 :-) Thanks |
There is http endpoint for OTLP format, I don't recall if it accepts OTLP JSON or only proto. There are no plans for Jaeger-native json. |
Jaeger collector does not have a REST API to collect Jaeger Thrift spans. There is no way to send spans from browsers to Jaeger collector.
A Zipkin REST endpoint exists at 9411 port. The Zipkin spans do not support everything, just like Jaeger span. For example: Zipkin does not have a way to reference spans
https://github.com/opentracing/specification/blob/master/specification.md#references-between-spans.
And, here is an open issue for that openzipkin/zipkin#1244
Is there a way we can directly send Jaeger span to Jaeger collector in JSON format using REST API?
The text was updated successfully, but these errors were encountered: