I'm also seeing this message. My otel config is here: https://gist.github.com/tmokmss/b6b0d639658161cd28519a65992866f9

packages versions are same as the OP.

Encountered the same issue and wrote a simple workaround while awaiting the actual fix to land:

import {
  Detector,
  DetectorSync,
  IResource,
  ResourceDetectionConfig,
  envDetectorSync,
  hostDetectorSync,
  processDetectorSync,
} from "@opentelemetry/resources"

function awaitAttributes(detector: DetectorSync): Detector {
  return {
    async detect(config?: ResourceDetectionConfig): Promise<IResource> {
      const resource = detector.detect(config)
      await resource.waitForAsyncAttributes?.()

      return resource
    },
  }
}

const sdk = new opentelemetry.NodeSDK({
  // ...
  resourceDetectors: [
    awaitAttributes(envDetectorSync),
    awaitAttributes(processDetectorSync),
    awaitAttributes(hostDetectorSync),
  ],
})

@timosaikkonen Your solution was really helpful!

I too faced same issue in my application , when I removed the below environment definition , the error is NO more appears . My application is built in nodejs

        - name: OTEL_LOG_LEVEL
          value: info

Anyone know the significance of this parameter and why error appear when I enable this on deployment ?

Thanks

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

Not stale.
Since the Detector type is deprecated in favor of DetectorSync, the current workaround may break in future releases.

It would be helpful if someone can share a stack trace of what is triggering the log message.

OTel SDK components should already be awaiting waitForAsyncAttributes() before accessing the resource attributes (examples), which should avoid the log message. If that's not the case, stack trace would be helpful as it may be a bug. Otherwise, it may be log spam.

If this is happening in your own code, just await waitForAsyncAttributes() before accessing the resource attributes.