We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently the Syslog parser assumes that events are generated in the same timezone, which might not be the case for every events or even host.
In BSD old style events, the timestamp ommits the timezone, we should provide an option to the input to set which timezone we should have.
In the newer* RFC5425 (or RFC3164 with RFC3339 timestamp) The timezone is a part of the string, so we should use that instead.
Quick search:
The text was updated successfully, but these errors were encountered:
Correctly parse ISO8601 dates with and without Timezone. (#7379)
49be9c8
Parses the following format: 2018-06-19 02:13:38 2018-06-19T02:13:38.635322-07:00 #7057
Fix is merged.
Sorry, something went wrong.
a9c5835
Parses the following format: 2018-06-19 02:13:38 2018-06-19T02:13:38.635322-07:00 #7057 (cherry picked from commit 49be9c8)
Correctly parse ISO8601 dates with and without Timezone. (elastic#7379)
a2c07d3
Parses the following format: 2018-06-19 02:13:38 2018-06-19T02:13:38.635322-07:00 elastic#7057 (cherry picked from commit 301d071)
No branches or pull requests
Currently the Syslog parser assumes that events are generated in the same timezone, which might not be the case for every events or even host.
In BSD old style events, the timestamp ommits the timezone, we should provide an option to the input to set which timezone we should have.
In the newer* RFC5425 (or RFC3164 with RFC3339 timestamp) The timezone is a part of the string, so we should use that instead.
Quick search:
The text was updated successfully, but these errors were encountered: