Orchestrator logs - precision in timestamps causes wrong order of log lines


#1

Hi,

A quick idea for Orchestrator logs

I have seen that logs are not in the correct order, when the timestamp is equal. I checked in the database and can see that the timestamp is not precise enough.

It seems that logs send to Orchestrator can be received in the wrong order and making the incremental ID misleading.

unnamed

Solution:

  • Add milliseconds precision to the timestamps

#2

The TimeStamp you see in the database is the one sent by the Robot.
You should not rely on Incremental Id for the logs, since there is a chance that the Robot - Orchestrator connection can drop, in which case the robot will send multiple logs saved locally to Orchestrator upon reconnect.


#3

You can play with the TimeStamp formatting in database logger target in web.config. In 18.1.1 we introduced this default formatting for the timestamp:

parameter name="@timestamp" layout="${date:format=yyyy-MM-dd HH:mm:ss.fff}"

PS: The format has to match to ones accepted by the SQL Server


#4

Hi @Alexandra_Olteanu,

Thank you for your answer.

This is on the Orchestrator server, right?

Would make sense it make this standard.