@timestamp not match with the log date

Generally this means that something that is not speaking the beats protocol is connecting to the input. Amongst the possible causes are:

  1. A beat with SSL enabled connecting to a beat input with SSL disabled
  2. A beat with SSL disabled connecting to a beat input with SSL enabled
  3. A port scanner (on the public internet you can be certain that folks are port scanning you, on a corporate network this may also happen)
  4. Someone else trying to use the same port