When rolling out with OpenTelemetry, ship both backends (HTTP requests and OpenTelemetry) with a feature flag to do a controlled rollout

[tferguson47]

Checklist

• I added a descriptive title
• I searched open requests and couldn't find a duplicate

What is the idea?

Idea:
When rolling out with OpenTelemetry, ship both backends (HTTP requests and OpenTelemetry) with a feature flag to do a controlled rollout
Desired State:
We have the ability to control which backend a user leverages when upgrading the plugin to use OTel

Why is this needed?

To do a controlled rollout in a safe way.

What should happen?

No response

Additional Context

Idea provided by Jannis in a knowledge transfer meeting about OTel. ( I am just documenting )

[travishathaway]

@tferguson47,

While I like the spirit of the issue, I think this will simply be included as a delivery requirement in other issues as we implement the next version of this plugin.

Let's keep this issue open though as a place to discuss possible approaches and things we'll want to watch out for.

[jezdez]

I've started the internal conversation about using Eppo as a backend to evaluate if this is an option for us as well. https://docs.geteppo.com/sdks/server-sdks/python/ has a good overview of what would be needed on the code side