-
Notifications
You must be signed in to change notification settings - Fork 106
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
filter/date: Improvements #66
base: master
Are you sure you want to change the base?
Conversation
Format: []string{time.RFC3339Nano}, | ||
Source: "message", | ||
Target: "@timestamp", | ||
TagOnFailure: []string{"gogstash_filter_date_error", "_dateparsefailure"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why TagOnFailure "_dateparsefailure" as a default value?
I mean there was "gogstash_filter_date_error"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was specifically to ensure some sort of compatibility with the output that logstash's date plugin dumps into elasticsearch, so I had added it to the list of tags added on failure to not break compatibility with anything anyone had been doing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's better to remove from default value, because not all users migrate from logstash, and it's unnecessary for pure gogstash user.
Write some examples or hints in README for your case?
071526d
to
71b89d1
Compare
Add'l parameters to add more logstash-like compatibility.