Ryan Fitzpatrick

@dependabot rebase

@carlosalberto, does this require a `FlaskScopeManager` in https://github.com/opentracing/opentracing-python that uses `_request_ctx_stack`? I'd be happy to take a crack at that if so. edit: Looking at the Tornado scope manager, it...

I've seen this too on 3.1.1, and will run into 100% cpu utilization when I set the waitDuration to something pretty high. This doesn't happen on 2.5.1. @assaf , are...

A note for the proposed manifest is that the observer extensions are primarily supported by the [receiver creator](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/receivercreator) so it would ideally be included as well.

>@rmfitzpatrick I don't know much about the receiver creator, but is it useful for monitoring Kubernetes or applications that run on Kubernetes? If not, I'd opt to remove the observer...

@akats7 what are you using the determine that the collection interval is increasing periodically? The collection occurs in a single-threaded executor service's [`scheduleAtFixedRate()`](https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/util/concurrent/ScheduledExecutorService.html#scheduleAtFixedRate(java.lang.Runnable,long,long,java.util.concurrent.TimeUnit)). The delay period is sourced from the...

>We could change to use [scheduleAtFixedRate](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ScheduledExecutorService.html#scheduleAtFixedRate-java.lang.Runnable-long-long-java.util.concurrent.TimeUnit-), but in your described situation this would likely cause several overlapping collections to attempt to execute, causing more issues with the JVM, in addition...

This would help in delivering https://github.com/open-telemetry/opentelemetry-java-contrib/issues/5 and since the jmx receiver in the collector doesn't allow running custom scripts I don't envision much friction as long as we are at...

https://github.com/open-telemetry/opentelemetry-java-contrib/pull/253 was opened to resolve this issue but there was pushback to the workaround and I wasn't able to track down the issue in how we interact w/ the sdk...

https://github.com/opentracing-contrib/java-agent/pull/45 resolves this by adding tracing command listener within `MongoClientSettings.builder()` calls.