Dynamic topic for googlecloudpubsub exporter

[JakubDaleki]

Component(s)

exporter/googlecloudpubsub

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

Different logs (for example from different files) should be written to different topics on GCP PubSub. Current implementation allows only to specify one destination topic in static yaml config.

Describe the solution you'd like

I want to add a new flag to config topic_from_attribute. If set to true each log should be sent to a topic specified in Attribute gcp.topic of a LogRecord. If attribute is not present or is in invalid format logs should be sent to default topic specified in the topic field.

My PR showing changes needed to obtain this mechanism: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33545/files

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/googlecloudpubsub: @alexvanboxel

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/googlecloudpubsub: @alexvanboxel

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

[JakubDaleki]

/label exporter/googlecloudpubsub discussion-needed

[github-actions]

Pinging code owners for exporter/googlecloudpubsub: @alexvanboxel. 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/googlecloudpubsub: @alexvanboxel

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

[alexvanboxel]

This can be considered, but first ordering will be added. This certainly will have an impact on the ACL's the service account needs. Before starting, I would review all the same classes of transport receiver/exporters that they have feature parity.

[JakubDaleki]

Thanks for your response @alexvanboxel. Is there any active thread to track progress of ordering feature so I can start working on this once ordering is added? If the work has not been started yet, I could contribute there as well.

[alexvanboxel]

Thanks for your response @alexvanboxel. Is there any active thread to track progress of ordering feature so I can start working on this once ordering is added? If the work has not been started yet, I could contribute there as well.

#32850

[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/googlecloudpubsubexporter: @alexvanboxel

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