open telemetry integration: how to avoid warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint

[vigouredelaruse]

i've risen to my natural level of incompetence with azure durable functions and open telemetry integration.

i'm searching for the root cause of an (c# in-proc .net6) orchestration that

• reliably prematurely halts at the same location
• was bulletproof before i instrumented the orchestration with opentelemetry
  as per

// function startup configuration
                var horselessTelemetryInstance = new HorselessOpenTelemetry(horselessSiteOptions);
                builder.Services.AddSingleton<IHorselessTelemetrySource>(horselessTelemetryInstance);
                var openTelemetrySourceName = horselessTelemetryInstance.ActivitySourceName; 
                var otel = builder.Services.AddOpenTelemetry();
                otel.ConfigureResource(resource => resource.AddService(serviceName: openTelemetrySourceName, serviceInstanceId: horselessClusterInstance.ClusterInstanceId.ToString()));
// etc

  public class TenantDeploymentOrchestrator : ITenantDeploymentOrchestrator, IHorselessWorkflowDeployment
  {
       public TenantDeploymentOrchestrator(
                                           IHorselessRedisClient redisClient,
                                           IHorselessTelemetrySource horselessTelemetry)
       {
          // etc
       }

        [FunctionName(nameof(TenantDeploymentOrchestration))]
        public async Task TenantDeploymentOrchestration(
            [OrchestrationTrigger] IDurableOrchestrationContext context, ILogger log)
        {
            var activityName = $"[FunctionName(nameof(TenantDeploymentOrchestration))]";
            using (var activity = horselessTelemetry.ActivitySource.StartActivity(activityName, ActivityKind.Internal))
            {
                log = context.CreateReplaySafeLogger(log);
                try
                {
                    var param = context.GetInput<TenantDeploymentOrchestrationModel>();
// etc
}

producing the following disappoint result

1>E:\src\horseless-core\src\workflow\horselessfx\horselessnewspaper.workflow.fx.rabbitmq\TenantDeploymentOrchestrator.cs(129,35,129,53): warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint.
1>E:\src\horseless-core\src\workflow\horselessfx\horselessnewspaper.workflow.fx.rabbitmq\TenantDeploymentOrchestrator.cs(268,79,268,97): warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint.
1>E:\src\horseless-core\src\workflow\horselessfx\horselessnewspaper.workflow.fx.rabbitmq\TenantDeploymentOrchestrator.cs(277,68,277,86): warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint.
1>E:\src\horseless-core\src\workflow\horselessfx\horselessnewspaper.workflow.fx.rabbitmq\TenantDeploymentOrchestrator.cs(305,77,305,95): warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint.
1>E:\src\horseless-core\src\workflow\horselessfx\horselessnewspaper.workflow.fx.rabbitmq\TenantDeploymentOrchestrator.cs(343,77,343,95): warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint.
1>E:\src\horseless-core\src\workflow\horselessfx\horselessnewspaper.workflow.fx.rabbitmq\TenantDeploymentOrchestrator.cs(456,35,456,53): warning DF0113: 'horselessTelemetry' violates the orchestrator deterministic code constraint.

where

• the error line numbers correspond to
• using (var activity = horselessTelemetry.ActivitySource.StartActivity(activityName, blah blah blah

is there a way to instrument [orchestrationtrigger] functions? please advise

[vigouredelaruse]

the root cause was identified as

• use of open telemetry api in [orchestration]
• use of async 'helper' method from [orchestration]

even if orchestrations can't be instrumented it's still possible to trace from queueproducer -> rabbitmq orchestration starter -> downstream [activititytrigger] as per

[fbarajas-fmg]

If I understand correctly, you removed OpenTelemetry from the orchestrator function and enabled it from outside of it? Do you think using it in Activities will be an issue?