David Luna

One last question from my side. I've checked that other metrics of time make use of `histogram` as instrument. Some examples: - https://github.com/open-telemetry/semantic-conventions/blob/cde003cd371ef8cc802f275bcfed15cff8fd6a48/model/metrics/jvm-metrics.yaml#L49 - https://github.com/open-telemetry/semantic-conventions/blob/cde003cd371ef8cc802f275bcfed15cff8fd6a48/model/metrics/go-metrics.yaml#L77 Here all the metrics related...

> > Here all the metrics related to delay and using s as unit use the gauge instrument. Probably a naive question but why is that? > > That is...

Ping to component owners @jj22ee @blumamir

closed in favour of #2376 following [this suggestion](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2329#discussion_r1687558761)

@weyert do you have time to address the changes proposed? I would be happy to merge this PR once done and the conflict is resolved.

@tzjames Is it possible to reproduce by checking out the source branch of [this PR](https://github.com/growthbook/growthbook/pull/2650) and run the app?

I think the approach 2 would be quite straight forward. The utility function to get processors from the environment vars is located at https://github.com/open-telemetry/opentelemetry-js/blob/fc0edd82f6749bfe1ca733ed1f80ad4a6015285f/experimental/packages/opentelemetry-sdk-node/src/utils.ts#L125 With that function being exported you...

@basti1302 @kirrg001 is it okay for you to have this breaking change? If not we I can instead add a new detector implementing the sync interface

Thanks @basti1302. Then we will go for the breaking change

> > > As discussed in the last SIG and documented on the PR, it is very unlikely that people out there are calling the `InstanaAgentDetector` directly and will be...