Currently, trace-summary will throw an error (Invalid starting time on line...) when trying to parse conn logs with a timestamp of type ISO8601 (if you are using something like redef LogAscii::json_timestamps = JSON::TS_ISO8601; to write Bro logs in JSON), for example 2019-03-01T21:16:50.629660Z. I believe this is due to this value trying to be interpreted as a float. This PR checks to see if the format is ISO8601, and if so, should convert the timestamp accordingly.
Currently,
trace-summary
will throw an error (Invalid starting time on line...
) when trying to parseconn
logs with a timestamp of typeISO8601
(if you are using something likeredef LogAscii::json_timestamps = JSON::TS_ISO8601;
to write Bro logs in JSON), for example2019-03-01T21:16:50.629660Z
. I believe this is due to this value trying to be interpreted as afloat
. This PR checks to see if the format isISO8601
, and if so, should convert the timestamp accordingly.