feat: accept spanProcessors from config

Author: Shaik-Sirajuddin

packages/cli-v3/src/entryPoints/dev-run-worker.ts

@@ -207,6 +207,7 @@ async function doBootstrap() {
       instrumentations: config.telemetry?.instrumentations ?? config.instrumentations ?? [],
       exporters: config.telemetry?.exporters ?? [],
       logExporters: config.telemetry?.logExporters ?? [],
+      spanProcessors : config.telemetry?.spanProcessors ?? [],
       diagLogLevel: (env.TRIGGER_OTEL_LOG_LEVEL as TracingDiagnosticLogLevel) ?? "none",
       forceFlushTimeoutMillis: 30_000,
       resource: config.telemetry?.resource,

packages/cli-v3/src/entryPoints/managed-run-worker.ts

@@ -188,6 +188,7 @@ async function doBootstrap() {
       forceFlushTimeoutMillis: 30_000,
       exporters: config.telemetry?.exporters ?? [],
       logExporters: config.telemetry?.logExporters ?? [],
+      spanProcessors: config.telemetry?.spanProcessors ?? [],
       resource: config.telemetry?.resource,
     });
 

packages/core/src/v3/config.ts

@@ -1,5 +1,5 @@
 import type { Instrumentation } from "@opentelemetry/instrumentation";
-import type { SpanExporter } from "@opentelemetry/sdk-trace-base";
+import type { SpanExporter, SpanProcessor } from "@opentelemetry/sdk-trace-base";
 import type { BuildExtension } from "./build/extensions.js";
 import type {
   AnyOnFailureHookFunction,
@@ -95,6 +95,14 @@ export type TriggerConfig = {
      */
     instrumentations?: Array<Instrumentation>;
 
+    /**
+     * Span processors to use for OpenTelemetry. This is useful if you want to add custom span processors to your tasks.
+     * There are executed in the order passed before running                         exporters
+     *
+     * @see https://trigger.dev/docs/config/config-file#spanProcessors
+     */
+    spanProcessors?: Array<SpanProcessor>;
+
     /**
      * Exporters to use for OpenTelemetry. This is useful if you want to add custom exporters to your tasks.
      *

packages/core/src/v3/otel/tracingSDK.ts

@@ -1,4 +1,5 @@
 import {
+  Context,
   DiagConsoleLogger,
   DiagLogLevel,
   TraceFlags,
@@ -66,6 +67,7 @@ export type TracingSDKConfig = {
   url: string;
   forceFlushTimeoutMillis?: number;
   instrumentations?: Instrumentation[];
+  spanProcessors?: SpanProcessor[];
   exporters?: SpanExporter[];
   logExporters?: LogRecordExporter[];
   diagLogLevel?: TracingDiagnosticLogLevel;
@@ -83,6 +85,7 @@ export class TracingSDK {
   public readonly getTracer: TracerProvider["getTracer"];
 
   constructor(private readonly config: TracingSDKConfig) {
+    console.log("tracing sdk constructor called");
     setLogLevel(config.diagLogLevel ?? "none");
 
     const envResourceAttributesSerialized = getEnvVar("TRIGGER_OTEL_RESOURCE_ATTRIBUTES");
@@ -120,6 +123,11 @@ export class TracingSDK {
 
     const spanProcessors: Array<SpanProcessor> = [];
 
+    //add span processor passed via config before exporters
+    for (const spanProcessor of config.spanProcessors ?? []) {
+      spanProcessors.push(spanProcessor);
+    }
+
     spanProcessors.push(
       new TaskContextSpanProcessor(
         VERSION,
@@ -139,10 +147,8 @@ export class TracingSDK {
           : new SimpleSpanProcessor(spanExporter)
       )
     );
-
     const externalTraceId = idGenerator.generateTraceId();
     const externalTraceContext = traceContext.getExternalTraceContext();
-
     for (const exporter of config.exporters ?? []) {
       spanProcessors.push(
         getEnvVar("TRIGGER_OTEL_BATCH_PROCESSING_ENABLED") === "1"