awss3exporter support mapping attributes

[Erog38]

Component(s)

exporter/awss3

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

When mapping logs to an S3 bucket for cold storage, every tenant / prefix needs to be associated with a unique exporter. This leads to a problem trying to use the routing exporter to route logs from centralized collectors.

Describe the solution you'd like

It would be fantastic if the AWS S3 exporter would support similar functionality as the splunk hec exporter allowing to map configuration values from resource attributes. This way incoming logs can be automatically routed based on incoming attributes. Namely the prefix attribute to start.

Describe alternatives you've considered

We've considered alternatives in order to route to unique exporters, but it would become too troublesome to manage over time.

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/awss3: @atoulme @pdelewski

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

[Erog38]

I would be open to attempting this work provided it's something that would be accepted.

[jkmdeltek15]

any updates if this will be worked on? this is a functionality that we also need so that the storage of relevant data should be segregated depending on tenant

a functionality similar to splunk exporter is actually good..

[Erog38]

I'm hopeful to get some feedback from others as well as the maintainers here to see if it's something worth bringing into this exporter such that it has some amount of continued support 😄

[atoulme]

I am open to adding this support, but I think you will need to stick around and become a codeowner to continue to maintain it. If that sounds good to you, please let me know and I will assign the issue to you.

[Erog38]

Thanks @atoulme! I have a coworker (@yshengli) who's open to taking this on and becoming a codeowner. I'll walk him through the process but will need an additional sponsor to help him become a member if you're open to it.

[Erog38]

@atoulme, sorry to hit you up again, but I'm hopeful you'd be willing to sponsor @yshengli to be a member and take this on.

[atoulme]

Your coworker is a tad too light in contributions. You also cannot be a sponsor ; you need approver or maintainer role to sponsor.

I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company

[Erog38]

Ah apologies, I'd thought that as an approver in contrib, I'd met that requirement.

I'm happy to own this in that case and can bring him on to lend a hand if that's okay with you.

[yshengli]

Hi all, I am glad to work on this feature and will be completing the PR recently. Kindly let me know if you have any thoughts, Thank you!

[Erog38]

I'll also be here and will submit a PR to be a codeowner tomorrow.