Syslog message (EventSource) creation date issue

14 hours ago, Stuart Weenig said:

This actually happens a lot, enabled by asynchronous data transfer. Particularly in our case, it needs to happen because there could be delays between when the event happens and when the data is received by the LM platform. 

There should be a field for the syslog time then, or include it in the message itself. But the actual alert date should be the time it hit LM (because that's the actual time where we received the notification - not 4/5 hours ahead of the REAL time in the portal).