-
Notifications
You must be signed in to change notification settings - Fork 151
Dynamic field values in prefix is not supported #16
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
Comments
Fix has been provided in https://github.com/nigoel/logstash-output-s3 |
I'd like to see dynamic values on prefix too. I want to collect my logs in daily folders and there is no option for it now. @nigoel maybe you should make a pull request since you already implemented a solution. |
+1 |
Any plans on implementing this? |
+1 |
2 similar comments
+1 |
+1 |
Would love this for all other string values like |
+1 |
Please merge it! |
1 similar comment
Please merge it! |
@nigoel would you pull the latest version and merge your changes? So your repo is up-to-date. That would be awesome!! I've tried, but got conflicts I couldn't solve. |
@nigoel I am using your version of the plugin as I needed dynamic prefixes. Workers stop after they've uploaded once. It seems need_cleanup? throws an error if @empty_downloads[prefix] is nil.
|
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
Adding +1 does not do anything, just spams us all. |
I am closing this issue in favor of #4, so all the discussion can happen in the same place. |
Creation of different file paths in s3 for different kind of events or tracking log file is not supported.
For example, here folder prefixes based on fields "app" and "type" are not supported.
input {
file {
path => "//data//executors//logs/"
}
}
filter {
grok { match => ["path","/%{GREEDYDATA}/executors/%{GREEDYDATA:app}[.]%{GREEDYDATA}/logs/%{GREEDYDATA:type}"]
}
}
output {
s3{
.....................
.....................
prefix => "applogs/%{app}/%{type}"
}
}
The text was updated successfully, but these errors were encountered: