Fixed year in time makes wrong data processing from past years

[ferrerogonzalo]

I had several trouble processing data from past year (2016) when running in 2017. I have commented the line 83 time.setYear(new Date().getFullYear()) // fix year to now in index.js

From this perspective the 'year setting' is wrong because it has nothing to do with the record you are processing.

Btw I am processing data from Juniper NAT Syslog.

[meschbach]

Do you have a sample log entry so I can build a test?

[gervasiocaj]

According to the Syslog RFC, this is the intended behaviour.

The TIMESTAMP described in RFC 3164 offers less precision than the
timestamp specified in this document. It also lacks the year and
time zone information. If a message formatted according to this
document needs to be reformatted to be in RFC 3164 format, it is
suggested that the originator's local time zone be used, and the time
zone information and the year be dropped. If an RFC 3164 formatted
message is received and must be transformed to be compliant to this
document, the current year should be added and the time zone of the
relay or collector MAY be used.