Skip to content
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

Open
untergeek opened this issue Feb 6, 2015 · 10 comments

Comments

@untergeek
Copy link

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.

@wiibaa
Copy link
Contributor

wiibaa commented Feb 6, 2015

sprintf additional behaviour also described in elastic/logstash#2315

@weiweiwang
Copy link

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.

@hakman
Copy link

hakman commented Jul 31, 2015

@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.

@weiweiwang
Copy link

thanks @hakman, I will put this problem to https://discuss.elastic.co/c/logstash

@mvernimmen-CG
Copy link

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.
So +1 for getting this feature added :)

@imweijh
Copy link

imweijh commented Jan 11, 2017

+1

3 similar comments
@trondvh
Copy link

trondvh commented Feb 14, 2017

+1

@mr2qin
Copy link

mr2qin commented Apr 1, 2017

+1

@leo100
Copy link

leo100 commented Feb 22, 2018

+1

@foxracle
Copy link

foxracle commented Aug 7, 2018

+1
this kind of output is very useful for file output like this:
output {
file {
path => "/test/%{+YYYY-MM-dd}.log"
}
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants