Skip to content

[receiver/awss3receiver] Introduce s3_partition_format like it is done in awss3exporter #43720

@mykola-elastic

Description

@mykola-elastic

Component(s)

receiver/awss3

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

When configuring AWS to write VPC Flow Logs/Cloudtrail Logs/... to S3 bucket it uses <year>/<month>/<day>/<hour>/ partitioning. However, awss3receiver uses a hardcoded partitioning year=<year>/month=<month>/day=<day>/hour=<hour>/ code.

It also adds logs_ to the file prefix with no possibility to override it. The file_prefix param only prepends the prefix, but the logs_ (or metric_/traces_) remain

Which results in "No telemetry found for time" messages

Describe the solution you'd like

  • Add a s3_partition_format parameter like it is done in awss3exporter link
  • Add possibility to override file prefix (for Logs telemetry type it is logs_) code

Describe alternatives you've considered

Workaround:

  • enable "Hive compatible partitioning" (option available for VPC Flow Logs)
  • set file_prefix to <aws-account-id>_vpcflow (the filename begins with <aws-account-id>_vpcflowlogs_<aws-region>_..., so it has logs_ in it)

Additional context

No response

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions