DAGMan is tailing the condor job log for the workflow and then creating
the ULOG_events in the dagman.out file.
When dagman reads in the events from condor job log , and the timestam
associated with the ULOG event is the dagman's own timestamp instead of the actualtimestamp reported in the condor job log.

In latest version of DAGMan, it will report the job log event timestamp in the end

12/02/15 16:45:35 Event: ULOG_SUBMIT for HTCondor Node NODERET (136.0.0) (12/02/15 16:45:32)

monitord needs to be updated to parse that and use it if specified.