-
Notifications
You must be signed in to change notification settings - Fork 901
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
Implement JSON in two other languages to ensure we are satisfied. #2797
Comments
I believe we have an implementation in Go (in the Collector) and in JavaScript (@dyladan can you please confirm?). |
Yes and I believe JS is the only language implementation |
Do we feel the need to implement it in one more language? In the Collector we have Go implementation of the OTLP/JSON receiver and exporter. |
only if we feel it would be useful. it's important for JS due to constraints on the runtime and on package size. this may also be of interest to android/ios where distributing protobuf/grpc may be unwanted bloat on the package? Possibly also for c/cpp where it may see use in embedded systems or similar restricted environments. |
In java we don't have an OTLP http/json protocol exporter, but we do have logging exporters which log in OTLP json format. The protocol part is pretty much the same with http/protobuf and http/json, so it should really just be the encoding that we're trying to increase confidence in. And java does have artifacts which produce the json encoding. |
I am going to close, but if anyone thinks we do need more implementations please feel free to reopen. |
No description provided.
The text was updated successfully, but these errors were encountered: