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

Doc enhancement for backup_add_prefix and backup_to_bucket #186

Open
shikrallah opened this issue Aug 27, 2019 · 0 comments
Open

Doc enhancement for backup_add_prefix and backup_to_bucket #186

shikrallah opened this issue Aug 27, 2019 · 0 comments
Assignees

Comments

@shikrallah
Copy link

The documentation for backup_add_prefix should mention that it does not have any effect unless the backup_to_bucket parameter is also specified.

In a related note it could be useful to mention that backup_to_bucket can be set to the same bucket that is being read from, and used in conjunction with backup_add_prefix to back up objects to a different path within the same bucket.

For instance a configuration such as the following could be used to store all objects in one bucket but avoid continually checking the older objects against the since DB to see if they had changed and/or avoid a new machine processing all old objects.

input {
s3 {
bucket => "source-bucket"
backup_to_bucket => "source-bucket"
backup_add_prefix => "processed"
delete => true
exclude_pattern => "processed"
}
}

or alternately

input {
s3 {
source => "source-bucket"
prefix => "data"
backup_to_bucket => "source-bucket"
backup_add_prefix => "processed"
delete => true
}
}

Regards,
Bill

@karenzone karenzone added the docs label Apr 15, 2020
@karenzone karenzone self-assigned this Apr 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants