Add a token to the configuration examples.

[CrowdHailer]

I'm trying to send my tracing data to lightstep.com

I have got to this instruction and have no idea what it means for this library, is there a standard token configuration option?

Lightstep Satellites need your project’s access token to accept the data. The recommended way to do this is to pass along your Lightstep access token in your Zipkin initialization:

[tsloughter]

I've not used lightstep. They likely have an example using the collector so might be easier to send to the collector and then to lightstep.

What does it say after Zipkin initialization:? I can't tell how it is adding it from that snippet.

[CrowdHailer]

There really isn't much more information, I can add a screenshot. I suppose the simplest thing.

I was looking at this digram and assuming I could just use the zipkin exporter to send data straight to the vendor ingest point, Which is what I was trying to set up with light step. That's because I couldn't work out where to run a collector in a heroku environment.

Is running without a collector a naive thing to be doing

[CrowdHailer]

More context, https://docs.lightstep.com/docs/use-zipkin-with-lightstep

So it looks like the access token, auth information should be added to the tracers default configuration.

From the docs here https://hexdocs.pm/opentelemetry_api/OpenTelemetry.Tracer.html#set_attributes/1
It sounds like setting attributes on a tracer just sets the attribute on the current (top?) span.

So these are the changes I have made to send data to lightstep did-app/glance@1d21427

[tsloughter]

Ah, I see, these docs are still OpenTracing based. It may work if you set the token in resources. You can set a resource with either an application env var or an OS var: https:/open-telemetry/opentelemetry-erlang/blob/master/apps/opentelemetry/test/otel_resource_SUITE.erl#L19