[8.19] (backport #8753) EDOT collector: include the forward connector. #8833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.




https://github.com/open-telemetry/opentelemetry-collector/tree/main/connector/forwardconnector
Include the forwardconnector, which we are highly likely to need for OTel native integrations to allow for unique processors per receiver without having to have unique pipelines with duplicate exporters.
To test this PR I used the following configuration showing how to have 2 filelog receivers that could have separate processors applied but export via the same exporter.
This is an automatic backport of pull request #8753 done by [Mergify](https://mergify.com).