I have been struggling a lot with the timestamps in Event Management events.
According to the EventAPI documentation, you can only set "time_of_event" with this format: "yyyy-MM-dd HH:mm:ss".
Also the case for the official Event Management documentation.
As far as I can tell, you can only get precision of 1 second on events, which is completely unacceptable for this application. This is a problem when multiple events happen in the same second. It should at least have millisecond precision.
The specific case is that I use a MID Server Connector to collect events from our Zabbix server. Some monitored systems can send events that are cleared in 50-100ms, and even though I use "SNEventSenderProvider.sendEvent()" to send the events in correct order, like they do in the build-in Zabbix connector, they randomly show up in incorrect order in ServiceNow.
The events are always resolved in correct order in Zabbix. I should mention we use a re-vamped version of the built-in Zabbix Connector script, that works for latest versions, but the event creation method is the same.
Is this really the quality of software we're paying for? Millisecond timestamps is an absolute necessity.
