Currently Consul logs (written to /var/log/upstart/consul.log at least for us) do not contain the timezone. This makes it difficult to accurately ingest the logs into a logging pipeline such as Logstash.
joshuaspence
All 6 comments
Oops, I meant timezone not timestamp.
joshuaspence
on 1 Aug 2016
@slackpad @joshuaspence I can tackle this. What should the format be for adding the timezone?
Currently a timestamp in the log looks like this:
2016/10/26 09:28:13 [INFO]
Should the timezone simply follow the time?
2016/10/26 09:28:13 PST [INFO] for example
mckennajones
on 26 Oct 2016
In my opinion, better to follow a well known standard
https://en.wikipedia.org/wiki/ISO_8601
would be much easier to parse.
romfreiman
on 26 Oct 2016
@rom-stratoscale I agree, standards all always nice. However, the Log package doesn't support that standard for some reason. There is an option to use UTC time instead but that's about it.
mckennajones
on 30 Oct 2016
Closing this against https://github.com/hashicorp/consul/issues/1249, which will hopefully allow this to be customized.
slackpad
on 18 May 2017
To format the date, this seems to work without using any fancy packages:
https://play.golang.org/p/RC9JxV_LaA
I'm not quite sure where I can use that snippet within Consul though. Seem to be a simple change but I don't know about how to integrate with the consul codebase.
mterron
on 3 Jul 2017
Related issues
deadjoe
路
4Comments
philsttr
路
3Comments
nicholasjackson
路
3Comments
powerman
路
3Comments
satheeshCharles
路
3Comments
Most helpful comment
In my opinion, better to follow a well known standard
https://en.wikipedia.org/wiki/ISO_8601
would be much easier to parse.