Headers Setter Extension Filtering Functionality

[kyo-ke]

Component(s)

extension/headerssetter

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

if new tenantID come to Tempo, it will automatically create tenant for that ID.
We want to allow only specific format for tenantID and avoid creating random tenant.

Describe the solution you'd like

Cerate filtering feature using regular expression on headers setter extension.
only matching tenantID is pushed to Tempo.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for extension/headerssetter: @jpkrohling. 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:

• extension/headerssetter: @jpkrohling

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

[atoulme]

Is there a way around this by using the transform processor to drop data if the tenant is not matching? @jpkrohling please review.

[kyo-ke]

In my understanding transform processor is for modifying telemetry and tenantID is in header so we cannot use it for this scenario

[atoulme]

Yes, you're correct. I don't know how to manipulate context headers.

[kyo-ke]

is it OK to create PR for this feature?

[jpkrohling]

This would likely be a good candidate for our middleware extensions: open-telemetry/opentelemetry-collector#7441