Processor needs to know the source of its data/signal like type and instance of receiver.

[mithunbelur]

Component(s)

cmd/otelcontribcol

Is your feature request related to a problem? Please describe.

Lets say, I have multiple receiver instances of same receiver type in a single pipeline.
I need to add a processor which can add resource attribute like source-ip : 10.0.0.1. Is this possible today. I coudnt find a way in processor to figure out which receiver pushed the data/signals.

receivers:
  mysql/mysql1/10.0.0.1:
    endpoint: 10.0.0.1:3306 
    username: username
    password: password
  mysql/mysql2/10.0.0.2:
    endpoint: 10.0.0.2:3306 
    username: username
    password: password

This is not just for mysql, I need to do it for other receivers as well. So I do not want to change receiver config to take in extra details. Is there some generic way to do it?

Describe the solution you'd like

It would be good if we have exact receiver name(including type/name) to be in context/scope for further processing in pipeline.

Describe alternatives you've considered

The possible way I could think of is using multiple pipelines each having only one receiver and add a separate attributes processor to add that attribute and then export it. Is there a better approach?
I cannot use instrumentation_scope.name as mentioned in the other issue #21466

Additional context

No response

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.