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

Docs incorrectly state processed_db_path can be left nil #28

Open
Evesy opened this issue Oct 15, 2024 · 0 comments
Open

Docs incorrectly state processed_db_path can be left nil #28

Evesy opened this issue Oct 15, 2024 · 0 comments

Comments

@Evesy
Copy link

Evesy commented Oct 15, 2024

Description:
The docs for input plugin specify:

If set, the plugin will store the list of processed files locally. This allows you to create a service account for the plugin that does not have write permissions. However, the data will not be shared across multiple running instances of Logstash.

This implies that it should be possible to omit processed_db_path and not have Logstash write to the local filesystem all the files it has processed, and instead rely solely on the metadata key and/or deleting processed files.

However processed_db_path is always assumed and the logic surrounding it cannot be avoided from what I can see

if @processed_db_path.nil?
ls_data = LogStash::SETTINGS.get_value('path.data')
@processed_db_path = File.join(ls_data, 'plugins', 'inputs', 'google_cloud_storage', 'db')
end

URL:

Example: https://www.elastic.co/guide/en/logstash/current/introduction.html

Anything else?

Not 100% clear if this is a documentation issue or the feature/support for not specifying the property was not correctly implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant