Consider detecting resources during initialization

[mwear]

• This only affects the JavaScript OpenTelemetry library
• This may affect other libraries, but I would like to get opinions here first

The SDK currently has resource auto-detection, but the detection must be user initiated. For example:

import { NodeTracerProvider } from '@opentelemetry/node`;
import { MeterProvider } from '@opentelemetry/metrics`;
import { detectResources } from '@opentelemetry/resources';

const resource = detectResources();
const tracerProvider = new NodeTracerProvider({ resource });
const meterProvider = new MeterProvider({ resource });
...

There are some detectors that make network calls to determine if they are running in a cloud provider (GCP, or AWS) to gather metadata, which introduces some latency. Ideally, resources will only be detected once and passed along as arguments where needed.

Is there a reasonable way that we can detect resources during initialization, without putting the responsibility on the user? Can we do so in a way that minimizes overhead, and possibly offer opt-out mechanisms for those who do not want or need this functionality?

[mwear]

It looks like these concerns are largely being addressed in: #1187

[mwear]

This is already being done and improvements are being discussed in #1533. Closing this issue.