Parse the timezone in PostgreSQL logs as part of the date #12338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsoriano
added
enhancement
review
[zube]: In Review
Team:Integrations
Parse the timezone in PostgreSQL logs as part of the date.
jsoriano
force-pushed
the
postgresql-date-timezone
branch
from
6e6c48f
to
ba6de6a
Compare
ruflin
reviewed
May 29, 2019
| @@ -1,6 +1,6 @@ | |||
| [ | |||
| { | |||
| "@timestamp": "2017-07-31T13:36:42.585Z", | |||
| "@timestamp": "2017-07-31T11:36:42.585Z", | |||
There was a problem hiding this comment.
This means we had previously a bug in here?
There was a problem hiding this comment.
I'd say so, yes. It was not using the timezone for date parsing before.
ruflin
reviewed
May 29, 2019
filebeat/module/postgresql/log/test/postgresql-9.6-debian-with-slowlog.log-expected.json
Show resolved
Hide resolved
ruflin
approved these changes
Jun 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Timezone in PostgreSQL logs is being parsed in a separated
field but then it is not being used for the final timestamp. Parse it
as part of the whole timestamp.