[exporter/prometheusremotewrite] Support dynamic AMP workspaces in endpoint

[neyp]

Is your feature request related to a problem? Please describe.
The exporter doesn't provide a way to assign a different Amazon Managed Service for Prometheus workspace according to incoming metrics.

Describe the solution you'd like
Route to different workspaces.

[jeromeinsf]

Hi @neyp

Thanks for logging this feature request. Could you detail what would be the routing logic based on? I suspect https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/routingprocessor is not dynamic enough?

[neyp]

Hey @jeromeinsf, we're planning to use one workspace per application/microservice and we would have to spin up dozens of exporters if we use the routing processor.

[github-actions]

Pinging code owners: @Aneurysm9. See Adding Labels via Comments if you do not have permissions to add labels yourself.

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

Pinging code owners:

• exporter/prometheusremotewrite: @Aneurysm9

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.