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

Syslog input should correctly parses the timezone from rfc3339 timestamp #7057

Closed
ph opened this issue May 9, 2018 · 1 comment
Closed

Comments

@ph
Copy link
Contributor

ph commented May 9, 2018

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:

urso pushed a commit that referenced this issue Jun 27, 2018
Parses the following format:
2018-06-19 02:13:38
2018-06-19T02:13:38.635322-07:00


#7057
@urso
Copy link

urso commented Jun 27, 2018

Fix is merged.

@urso urso closed this as completed Jun 27, 2018
adriansr pushed a commit that referenced this issue Jul 23, 2018
Parses the following format:
2018-06-19 02:13:38
2018-06-19T02:13:38.635322-07:00

#7057
(cherry picked from commit 49be9c8)
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
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)
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