Tyler Helmuth

@ChrsMark ya I'd prefer that the `NewNodeSharedInformer` stuff be moved to its own PR. Doing that will keep us aligned with our [contributing guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CONTRIBUTING.md#refactoring-work).

@dmitryax @povilasv please give this another look

@michalpristas I suspect this is doable via regular expression, and any converter would be doing regex internally. Can this be accomplished with [`ExtractPatterns`](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/ottlfuncs/README.md#extractpatterns)?

> I would be okay adding this. We can use the url.Parse stdlib function instead of having regular expressions either in a statement or in our code. In general I...

@michalpristas can you open a PR with these suggestions in `ottlfunc` README at the bottom so we can continue the discussion and codify the rules.

Probably related https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33153

@atoulme @crobert-1 @cparkins I will get a semconv issue/PR opened to add the net-new attribute names. As for the mapping of azure fields to existing fields, I do not believe...

@lkwronski I totally lost track of this PR, but I am still interested. I'd like other reviews before adding the net-new feature.

Opened https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32465 to fix that link

@lkwronski that link is fixed, we'll merge this once you handle the go mod file