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



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.



  • Add milliseconds precision to the timestamps