-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Normalize timestamp time zones #4569
Comments
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jul 12, 2017
During event normalization convert any time objects to a common.Time and ensure that the time zone is UTC. Fixes elastic#4569
ruflin
pushed a commit
that referenced
this issue
Jul 14, 2017
During event normalization convert any time objects to a common.Time and ensure that the time zone is UTC. Fixes #4569
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jul 17, 2017
During event normalization convert any time objects to a common.Time and ensure that the time zone is UTC. Fixes elastic#4569 (cherry picked from commit 29f4cc7)
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jul 17, 2017
During event normalization convert any time objects to a common.Time and ensure that the time zone is UTC. Fixes elastic#4569 (cherry picked from commit 29f4cc7)
Branches that have been patched: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Index names that contain dates may be incorrect when the system timezone is not in UTC. The index name (
<beatname>-%{+yyyy.MM.dd}
) is generated based on the internal@timestamp
value. The date formatter that converts the%{+yyyy.MM.dd}
into a date doesn't do any conversion to UTC.Some Beats may normalize their timestamps to UTC before publishing events and they will not be affected by this bug.
For confirmed bugs, please report:
The text was updated successfully, but these errors were encountered: