-
Incident report
-
Resolution: Fixed
-
Minor
-
None
-
2.1.9
I've created a network discovery rule do scan for web servers with a 60 second delay, enabled it and started the server. It generated a bunch of events, but some event IDs do not match the chronological order. Here's an example:
mysql> SELECT * FROM events LIMIT 4
-> ;
----------------------------------------------------------+
eventid | source | object | objectid | clock | value | acknowledged | ns |
----------------------------------------------------------+
1 | 1 | 2 | 1 | 1382594233 | 2 | 0 | 0 |
2 | 1 | 2 | 1 | 1382594233 | 0 | 0 | 0 |
3 | 1 | 1 | 1 | 1382594230 | 2 | 0 | 0 |
4 | 1 | 1 | 1 | 1382594230 | 0 | 0 | 0 |
----------------------------------------------------------+
4 rows in set (0.00 sec)
Note, that event 1 and 2 happened after 3 and 4. I haven't changed any discoverer process settings.