Exporter with Filter to triage traces with different rules

[LynnLi11]

Issue that does not fit into other categories

What are you trying to achieve?
We have few exporters in our project and once activities being produced, they will be all exported to every exporter under the sampling rule. But sometimes we only need some of the activities being exported to one exporter and others being exported to another.

What do you expect to see?
I expect there would be a filter or some filter action before the actual exporting action.

Additional context.

[Add any other context about the problem here. If you followed an existing
documentation, please share the link to it.]
I create a draft PR to raise the proposal:

1. Add a processor which contains a filter instead of the original processor which Geneva exporter or console exporter use. Then it can control which activity will be filtered and which would be left and exported. (Add exporter processor with filter to control the activities be exported to different exporters #1453)
2. However, I think these extensions should be moved to relevant exporter extensions to keep pace with the exporter upgrading.

Anyone could help review my PR and give some suggestions?

[cijothomas]

Can you using FilteringProcessor to achieve this? None of the official exporters from OTel spec has exporter level filtering ability, so they need to come via spec first before being considered. For any other exporters, open a specific issue so that the owners of that exporter can comment on their thoughts.

[martinjt]

The way this should be done is using the OpenTelemetry collector. It is a much better solution due to it offloading the processing and therefore reducing the memory used and CPU inside the .NET application.

Closing this issue as there was no response for 4 months.