Adding the scan_start_tstamp that is in the cap_state file to the log file for the capture job would be useful for troubleshooting and monitoring capture jobs. Especially when captures are archive_only and low/sporadic volume. Seeing the scan_start_tstamp not advancing in the log even though the capture job cycling is logged would be a quick way to spot issues with the capture job that is not generating an error. For example, there are no new archives to process by the capture.