Alex Boten

@nslaughter thanks for proposing the component, i'm happy to sponsor it. Instead of a separate `host`/`port` configuration, it would be more consistent w/ other receivers to use `endpoint` to include...

> 1. Add a setting to our "service.CollectorSettings" for the Collector instance to watch or not for config provider updates. Maybe disabled by default, and allow a flag to set...

As discussed in the SIG meeting on Mar 23, it may be helpful to provide a solution for all components, not just the scrapers.

@jpkrohling here's what i've done so far in my pr https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/10904: - created a workspace: `go work init` - added all the components: `go work use -r .` - removed...

> I remember seeing that there's something special about releasing modules that are part of workspaces, but I'll read the docs again and summarize my understanding. Based on what I'm...

> I'm now at a point where I'm doubting we will be gaining any improvements by using go.work, given that our main goal was to indeed reduce the replace statements...

Would be happy to sponsor this. Couple of questions: 1. Is it worth including a method for the check? 2. Does make sense to make it possible to check multiple...

@philipcwhite is this component still something you're actively working on? if not i'd be happy to take it over.

@rahuldimri all yours!

One question that comes to mind when looking at this list, are we planning on releasing these packages independently in the future? If so we'll need to figure out what...