Sam

Any thoughts here @picandocodigo? Happy to keep things contained in `opentelemetry-ruby` (i.e. do option 1 or 2) but if option 4 is workable, that would probably be cleaner 😄

> Hi @plantfansam, Sorry, I've had quite a busy couple of weeks! Let me look into this in detail and talk with the team and I'll get back to you...

@jtmalinowski to make sure I understand, you're saying that the configurator's [`add_span_processor` method](https://github.com/open-telemetry/opentelemetry-ruby/blob/672739120a605c5c14afc48e5aa07d1320443355/sdk/lib/opentelemetry/sdk/configurator.rb#L127) is not a satisfactory solution because a env var-based configuration is more user-friendly?

I did a little research into this ticket, and I wanted to get some clarification before trying anything silly. Please forgive any naivete, as I'm new to Open Telemetry! So...

Ah, wonderful! Thanks so much for the clarification. I'll try to start with EC2 and see where it leads.

@arielvalentin yes, exactly!

Thanks @chrisholmes! Are you set up with a tracing UI locally? If so, would it be possible to include a screenshot of a `racecar` trace? This isn't part of our...

@bixu are you able to provide reproduction steps? You may want to use the [bug issue template](https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/main/.github/ISSUE_TEMPLATE/bug_report.md).

Ah, I was confused — no reproduction steps necessary. @ericmustin beat me to it — not sure why we are requiring `1.1.0`. I guess we could generate an appraisal with...

I'm with @ahayworth on this one - would prefer not to introduce the complexity associated with supporting super-old versions.