wrong event time of connect/disconnect

[dsnz]

hello,

I noticed that when a device is down (disconnects),
the event time is not really the time the first scanner noticed it (the earliest time) but it's the time the 'Process Scan' runs and presumably makes a final event record and sends the notification (this description is my understanding, I don't really know the details of netalertx operation)
the time difference can be up to 2 minutes
I suspect that the same thing happens when a device connects again (ie. connection event time is later than true one) but I did not happen to check the logs for this until now

can you change the logic so that the correct event time is recorded ?

ref discussion

[jokob-sk]

This is by design, can't currently make it faster, will look into it if more people request it.

[dsnz]

hmm , is it a matter of speed ?

I think the time a scanner run last time is recorded along with its results
so , the obvious thing is to just set that time and not the current time when processing

if the scanner time is not recorded then
a feature request would be to record it and be able to set the correct event time later

[jokob-sk]

Feel free to open a PR to fix it if you know how to improve this. I didn't face such an issue before.