Nodejs instrumentation - Propagator "xray" requested through environment variable is unavailable.

[ademar-prothon]

We are unable to use the xray propagator on an auto-instrumented nodejs app. Env : k8s on eks v 1.26.4

Instrumentation :

apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: exchange-platform
  namespace: default
spec:
  exporter:
    endpoint: http://xray-collector-collector.default.svc.cluster.local:4318
  propagators:
    - xray
  sampler:
    type: always_on
  nodejs:
    image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-nodejs:latest
    env:
      - name: OTEL_EXPORTER_OTLP_ENDPOINT
        value: http://xray-collector-collector.default.svc.cluster.local:4317
      - name: OTEL_LOG_LEVEL
        value: info

Error message : Propagator "xray" requested through environment variable is unavailable.

Any ideas ? Thanks !

[TylerHelmuth]

@ademar-prothon thanks for bring this to our attention. For this to work we need to modify this file and the package.json to include the xray propagator. Is this something you'd like to work on?

[fracampit]

just hit the same problem. Is there any that can be done at our end, or is xray currently unavailable for NodeJs instrumentation?

08-03-2023 01:37:30 PM Propagator "xray" requested through environment variable is unavailable.
08-03-2023 01:37:30 PM Starting OpenTelemetry
08-03-2023 01:37:26 PM $ node -r ./tracing.js ./server.js

[TylerHelmuth]

@fracampit We need the NodeJS sdk updated: https://github.com/open-telemetry/opentelemetry-operator/pull/1872#discussion_r1253770528

[fracampit]

@fracampit We need the NodeJS sdk updated: #1872 (comment)

Thanks for the update. I'll keep an eye on this space then :)

[adityamehra]

Hello @TylerHelmuth Was this issue fixed by https://github.com/open-telemetry/opentelemetry-js/pull/4554?

[fracampit]

Any updates on this?

[garysassano]

I confirm that the error is still present.

[jungjinlee-plugo]

@garysassano For reference here, 'Cannot redefine property: handler' error can be solved. https://github.com/aws-observability/aws-otel-lambda/issues/284#issuecomment-1465465790