I put above example in a minimal app: https://github.com/ioolkos/otel_example/. I still must be missing some basic step in the setup, as I don't see that span exported.
Tristan Sloughter
@tsloughter
oh, I bet the sampler arg isn't working
becuase the way it is setup in your _app is slightly wrong
better to just put this stuff in a sys.config and add the apps to applications in the .app.src :)
ioolkos
@ioolkos
sure, just wanted to be as dynamic and explicit as possible
great stuff :)
Tristan Sloughter
@tsloughter
cool
_
ioolkos
@ioolkos
thanks for your help
ioolkos
@ioolkos
I noticed ?set_status(?OTEL_STATUS_OK) doesn't set status.code to 1 in opentelemetry-collector pipeline to jaeger. Always stays 'unset' and 0 in jaeger. But I guess that's an issue of the collector, not otel-erlang. (and there's also a set of deprecated status codes, it seems)
All that's let is to send the traces to somewhere I can usefully view them. i.e. replace the stdout exporter.
What would anyone recommend using for local development.
Peter Saxton
@CrowdHailer
I see a datadog setup in the examples repo but cant work out if the locally running agent will show my traces or if I need to send them to an account I have with datadog
Peter Saxton
@CrowdHailer
So it looks like Jaeger and zipkin are my choices for running a collector and ui locally.
Tristan Sloughter
@tsloughter
yea
Peter Saxton
@CrowdHailer
I've also moved on to using the opentelemetry_exporter I can only find docs on jaeger about supporting protobuf.
not sure what else exists, opentelemetry collector might have a visualization option in its contrib repo
Tristan Sloughter
@tsloughter
and the update to the zipkin exporter to 0.5.0 shouldn't be much to change
Chulki Lee
@chulkilee
Hi - I'm working on improving docs - open-telemetry/opentelemetry-erlang#176 - and I have a few questions. 1) I see this gitter room is mentioned in one of README. Is this the place to join? Then I'll add it to all README
Chulki Lee
@chulkilee
Also.. do we have benchmark? seems like c25ac353602cf1ce8d655e2f5c7e850e147151ce removed code from samples.
Tristan Sloughter
@tsloughter
if I remember correctly the benchmarks were removed because the particular ones didn't make sense anymore and none have been added since
this gitter is like the official opentelemetry channel for the Erlang SIG. but discussion also happens through the Erlang Ecosystem Foundation observability working group channel in the Erlang slack