-
Notifications
You must be signed in to change notification settings - Fork 43
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
Make the ISO-8601 Time output configurable (timezone specific instead of always Zulu) #10
Comments
sprintf additional behaviour also described in elastic/logstash#2315 |
I'm a Chinese developer, our timezone is +08:00,the problem using logstash is that @timestamp is always formatted as @timestamp" => "2015-07-25T16:00:30.000Z, the input time is 2015-07-26 00:00:30. This problem will cause 1 day log to be spliced to two indexes:logstash-2015.07.25 and logstash-2015-07.26 I tried to fix it by add logged_date field to represent 2015-07-26 in +08:00 timezone, however, in kibana, all the date fields will be added 08:00 hours, which causes incorrect logged_date in Chinese timezone Could anyone give me a solution on this problem? I googled around and found no proper solution. |
@weiweiwang you might want to take a look at the timezone option. If you want to ask more questions, I suggest using https://discuss.elastic.co/c/logstash. |
thanks @hakman, I will put this problem to https://discuss.elastic.co/c/logstash |
Having an option to specify the timezone for output would be great. Currently any file we write out of logstash which uses timestamp, writes it in UTC. This is not what we want. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+1 |
Migrated from: https://logstash.jira.com/browse/LOGSTASH-520
Migrated from: https://logstash.jira.com/browse/LOGSTASH-2243
The desire expressed in these tickets is that a timezone other than Zulu/UTC be able to be output from the date filter. Not every output goes to Elasticsearch or uses UTC.
The text was updated successfully, but these errors were encountered: