Opt-out of distributed tracing / context propagation

[fabianmeyer]

I'm currently running the following setup:

• A timer triggered function that acts as a watch dog, scheduling / terminating orchestrators (e.g. scheduling a new orchestrator for each newly enrolled IoT device and terminating the running orchestrator for each decomissioned device)
• Eternal orchestrators that call an actvity, continue as new and block on a timer until the next schedule
• Activities that perform a certain task (e.g. calculating some statistics for the device)

Overall, the setup works pretty well, but the distributed tracing gives me a headache. I have one giant, infinite OTEL trace, originating from the timer function and spanning over all orchestrators and activities. My goal would be to have a new trace for each continue as new of each eternal orchestrator. I've tried to opt-out of the context propagation by setting "DistributedTracingEnabled": false, but this only seems to affect the control queue and not the history table (ParentTraceContext is still always set to the root trace).