-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[config] logging.useUTC -> logging.timezone #21561
Conversation
💔 Build Failed |
docs/setup/settings.asciidoc
Outdated
@@ -73,7 +73,7 @@ error messages. | |||
|
|||
[[logging-verbose]]`logging.verbose:`:: *Default: false* Set the value of this setting to `true` to log all events, including system usage information and all requests. Supported on Elastic Cloud Enterprise. | |||
|
|||
`logging.useUTC`:: *Default: true* Set the value of this setting to `false` to log events using the timezone of the server, rather than UTC. | |||
`logging.timezone`:: *Default: UTC* Set to the canonical timezone id to log events using that timezone. |
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.
Can we link here? https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
And provide an example like US/Pacific
?
I am concerned that folks will not easily understand what the "canonical timezone id" they need to provide would be.
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.
Added with 9629036.
💚 Build Succeeded |
💔 Build Failed |
retest |
💚 Build Succeeded |
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
Looks like there is a conflict with the docs. Want to resolve that and merge this PR? |
💚 Build Succeeded |
This reverts commit f6e9090833a5180fe360a9ff54543c37c0ca3a58.
💚 Build Succeeded |
@jbudz What's the status here? |
good to go, i'm going to do a fresh ci run with master merged and then i'll get it committted |
💚 Build Succeeded |
* [config] logging.useUTC -> logging.timezone * docs * [env] exit if starting as root * fix import path * add link and timezone example * Revert "[env] exit if starting as root" This reverts commit f6e9090833a5180fe360a9ff54543c37c0ca3a58.
* [config] logging.useUTC -> logging.timezone * docs * [env] exit if starting as root * fix import path * add link and timezone example * Revert "[env] exit if starting as root" This reverts commit f6e9090833a5180fe360a9ff54543c37c0ca3a58.
This deprecates logging.useUTC and replaces it with logging.timezone. The default timezone is still UTC. To use a local timezone set
logging.timezone: false
We'll have a followup PR targeting 7.0 to remove the deprecation notice and default to a local timezone (and remove the optional 'false' schema).Explicit timezones help in situations such as docker containers where the system timezone isn't necessarily setup to be your timezone.
Closes #11038.