-
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
Remove convert_timezone
option from filebeat system module
#12410
Remove convert_timezone
option from filebeat system module
#12410
Conversation
Timezone is now obtained from the system where filebeat is running, and timezone conversion when parsing the timestamp is always done. This timezone information is included in the `event.timezone` field, it can be overriden with the `add_fields` processor, or removed with the `remove_fields` processor.
1059f14
to
ae43ca3
Compare
👍 to this change, I would update docs to explain how timezone works and how to override it. It could be a block attached to all these modules, like we do with Metricbeat HTTP & SSL settings:
This will also need a changelog (breaking change) |
fce63bf
to
c0e0053
Compare
@exekias I have added the documentation as a new file that can be imported, so it can be added to the documentation of any module, after the settings section, like this: |
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.
LGTM. It's kind of a breaking change but at the same time a bug fix :-)
It's great that in case we find later a case where it is actually a breaking change (I hope not) there is a workaround by with removing the processor or removing the field.
To disable this conversion, the `event.timezone` field can be removed with | ||
the `drop_fields` processor. | ||
|
||
If logs are originated from systems or applications with a different timezone to |
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 assume that is for the syslog case etc?
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.
For example. But this can really happen in any case where the application generating the logs is configured with a different timezone than metricbeat.
I think this can be moved out of draft :) |
Apply elastic#12410 to the rest of modules.
Timezone is now obtained from the system where filebeat is running, and timezone conversion when parsing the timestamp is always done. This timezone information is included in the `event.timezone` field, it can be overriden with the `add_fields` processor, or removed with the `remove_fields` processor. Apply #12410 to the rest of modules.
…#12410) Timezone is now obtained from the system where filebeat is running, and timezone conversion when parsing the timestamp is always done. This timezone information is included in the `event.timezone` field, it can be overriden with the `add_fields` processor, or removed with the `remove_fields` processor.
Timezone is now obtained from the system where filebeat is running, and
timezone conversion when parsing the timestamp is always done. This
timezone information is included in the
event.timezone
field, it canbe overriden with the
add_fields
processor, or removed with theremove_fields
processor.Closes #11858