Some Kibana log messages have timestamp 1970-01-01T00:00:00Z

[LeeDr]

Kibana version: 6.5.0-SNAPSHOT

Elasticsearch version: 6.5.0-SNAPSHOT

Server OS version: Ubuntu 14

Browser version: n/a

Browser OS version: n/a

Original install method (e.g. download page, yum, from source, etc.): tar.gz

Describe the bug: Some log messages must be sending 0 for the timestamp to log?

{"type":"log","@timestamp":"1970-01-01T00:00:00Z","tags":["debug","legacy","service"],"pid":1900,"message":"Kibana server is not ready yet GET:/app/kibana."}
{"type":"log","@timestamp":"1970-01-01T00:00:00Z","tags":["debug","legacy","proxy"],"pid":1900,"message":"Event is being forwarded: connection"}
{"type":"log","@timestamp":"1970-01-01T00:00:00Z","tags":["debug","legacy","service"],"pid":1900,"message":"Kibana server is not ready yet GET:/favicon.ico."}
{"type":"log","@timestamp":"2018-09-21T21:14:26Z","tags":["info","optimize"],"pid":1900,"message":"Optimization of bundles for ml, stateSessionStorageRedirect, status_page, timelion, graph, monitoring, login, logout, dashboardViewer, apm and kibana complete in 357.33 seconds"}

Steps to reproduce:

1. watch kibana.stdout

Expected behavior: Should have current date/time timestamps

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[tylersmalley]

@elastic/kibana-platform

[epixa]

@azasypkin Think it's possible for the debug log type to have different behaviors than others? That or logs from the new platform aren't setting date properly...

[azasypkin]

Think it's possible for the debug log type to have different behaviors than others?

Nope, log level shouldn't affect the behaviour.

That or logs from the new platform aren't setting date properly...

Yeah, looks like it's. New platform uses timestamp property, but log reporter expects @timestamp. We use Date.getMilliseconds() in the core, when we should use Date.getTime().

I'm surprised I haven't noticed that earlier, my bad. Luckily new platform doesn't log anything important right now, 6.4 isn't affected and the fix is trivial - I'll take care of it on Monday.