Log output should include timestamp
Description
testing discovered
Gliffy Diagrams
Activity
Philippe Weber August 1, 2014 at 7:56 AM
Closing in favor of centralising discussion about internal logging in https://github.com/elasticsearch/logstash/issues/1569
Andrew Rowson March 26, 2013 at 2:20 PM
Hmmm, I'm using the --log switch, and my log messages look like this:
{:message=>"Could not start TCP server: Address in use", :host=>"0.0.0.0", ort=>5144, :level=>:error}
{:message=>"Using experimental plugin 'syslog_pri'. This plugin is untested and may change in the future. For more information about plugin statuses, see http://logstash.net/docs/1.1.9/plugin-status ", :level=>:warn}
Can't see a timestamp there...
Jordan Sissel March 25, 2013 at 6:59 PM
I'm still on the fence if the current behavior (output is terminal == output human-ish readable) is good, though.
Jordan Sissel March 25, 2013 at 6:58 PM
Logstash's logger detects if the output is a terminal, and if so, tries to output somewhat human-readable messages that do not include a timestamp on the assumption that you'll only output to a terminal if you are actually watching the output.
If you have logstash log to a file, instead, it will include timestamps.
Details
Details
Assignee
Logstash DevelopersReporter
Andrew Rowson
The current log format is currently missing any timestamp data for when the log entry was written. This can make it difficult to correlate events and generally figure out when any issues occurred.
It'd be useful if the log output included a timestamp value.