Add a on-demand type of receivers to enable scrape data as needed

[larryck]

Component(s)

No response

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

In my case, I cannot scrape data all the time due to storage cost and performance impact. I need a way to start/stop the receivers as needed.

Describe the solution you'd like

1 divide receivers into on-demand receivers and long-running receivers.
2 develop a configuration service which user can send start/stop data scrape requests to;
3 the collector starts on-demand receivers after getting startup requests and stop them similarly;
4 the data processing pipelines work unchanged.

Describe alternatives you've considered

No response

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.

[atoulme]

This is too vague of a request - please see OpAmp to manage collectors remotely? This might be an applicable solution for your use case.

[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.