The addSpanProcessor method is deprecated in the OpenTelemetry JS SDK. The recommended approach is to use the spanProcessors property when constructing your TracerProvider. This makes your tracing setup more declarative and aligns with current best practices.

Here's how you can migrate your code:

import { NodeTracerProvider } from "@opentelemetry/sdk-trace-node";
import { BatchSpanProcessor } from "@opentelemetry/sdk-trace-base";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-proto";
import { resourceFromAttributes } from "@opentelemetry/resources";
import { SEMRESATTRS_PROJECT_NAME } from "@arizeai/openinference-semantic-conventions";

const provider = new NodeTracerProvider({
  resource: resourceFromAttributes({
    [SEMRESATTRS_PROJECT_NAME]: "your-project-name",
  }),
  spanProcessors: [
    new BatchSpanProcessor(
      new OTLPTraceExporter({
        url: "http://localhost:6006/v1/traces",
      })
    ),
  ],
});

provider.register();

This pattern replaces the old provider.addSpanProcessor(...) call and is now the preferred way to add span processors in OpenTelemetry JS SDK (example & rationale). If you use the phoenix-otel package, you can further simplify setup by using its register function, which abstracts away manual provider and processor configuration (migration example).

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

[js] addSpanProcessor is deprecated #2372

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions