Closed denic closed 4 years ago
Thanks. I bet the protos changed again :(. They aren't yet considered stable so they keep changing. It should go GA in September and then this issue won't keep coming up.
I'll verify and upgrade the protos later this morning and let you know.
Are you using the hex package? Have you tried using the git repo? I think there might be updates not released yet.
The changes I found in the protos is unrelated to the attributes, but I am fixing it up and will have a PR, but I think you might see it working if you simply switch to the git repo until we have another release made, which can be soon.
I don't believe we've cut a release in a while so that looks like the issue with the old protos. https://github.com/opentelemetry-beam/opentelemetry_exporter/commit/c2e495065620cc6c06c57786b8db724b02367f27 is stable and should correct the issue you're seeing.
Are you using the hex package?
Jepp :) Switched to using the git repo. Now everything looks fine. Thanks guys!
And thanks for the work you put into this project.
@denic ok, good to hear. Will get a release out after I get a new PR in with the latest updates to the proto and we'll have to try to keep updating the package more often :). Hopefully GA comes soon and there won't be so many changes.
@tsloughter they haven't cut a new release of the protos yet, so I think we should hold off on that. The current commit we're at is the last release (0.4.0).
Eh, if the collector keeps moving we should keep updating to keep up. I guess if the collector only has specific releases.
The collector is tied to the protos release. It isn't tied to the nightly afaik. There are breaking changes in the unreleased protos that we're going to have to address across the main API and SDK, as well, like this one https://github.com/open-telemetry/opentelemetry-proto/commit/ca6dcbbf390d8b3ce419a931eb351d189a3eb4fa.
Maybe we just set up a branch to work against with the latest protos and be ready to release when they do. We should also probably add a compatibility matrix in the README.
Hi,
I try to use opentelemetry_exporter from an Elixir application. I use the opentelemetry-collector to receive the traces and export it to Zipkin and Jaeger (see Attachments). For my test setup I added instrumentation to Plug and create a trace as follows:
The problem now is, that only the attributes keys (xxx.num, xxx.string) are visible in Zipkin/Jaeger, not the values.
I added a debug statement right before the protobuf conversion and after it (in https://github.com/opentelemetry-beam/opentelemetry_exporter/blob/master/src/opentelemetry_exporter.erl#L44).
I use
opentelemetry_exporter_trace_service_pb:decode_msg(Proto, export_trace_service_request)
to decode. It results in the following snippets.To me it looks like the values are somehow lost in the conversion.
Any hint to what I am doing wrong is much appreciated! Thanks.
PS: Besides that also using gprc protocol does not work, but that maybe a story for another issue. :)
Atachments
opentelemetry-collector config