Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for dynamic attributes in S3 prefix for AWS S3 Exporter #29872

Closed
shokada opened this issue Dec 13, 2023 · 3 comments
Closed

Add support for dynamic attributes in S3 prefix for AWS S3 Exporter #29872

shokada opened this issue Dec 13, 2023 · 3 comments
Labels

Comments

@shokada
Copy link

shokada commented Dec 13, 2023

Component(s)

exporter/awss3

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

We are currently unable to dynamically include pod annotations in the s3_prefix when using the AWS S3 Exporter with the OpenTelemetry Collector. We want to organize our S3 object paths with pod-specific information to easily identify and categorize logs from different pods.

Describe the solution you'd like

We would like the AWS S3 Exporter to be enhanced to support dynamic attributes in the s3_prefix. This would allow us to construct S3 object paths that include values from specific attributes, such as pod annotations. For example, we could use the logging/prefix annotation from a pod's metadata to structure the path like so:

pod_log/cluster_name=${cluster_name}/namespace_name=${namespace_name}/prefix=${logging/prefix}/year=XXXX/month=XX/day=XX/hour=XX/

Describe alternatives you've considered

As an alternative, we are considering using Fluent Bit, which supports dynamic values in the S3 object key configuration. This would allow us to include pod-specific annotations in the S3 paths. However, we would prefer to use OpenTelemetry Collector if it supported dynamic attributes in the S3 prefix, as it would keep our observability stack consistent and leverage OpenTelemetry's advanced processing capabilities.

Additional context

No response

@shokada shokada added enhancement New feature or request needs triage New item requiring triage labels Dec 13, 2023
Copy link
Contributor

Pinging code owners:

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

Copy link
Contributor

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:

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

Copy link
Contributor

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant