SOLVED What's the CloudSync API call's time format?

Joined
Dec 28, 2020
Messages
18
Hey folks,

I'm trying to use the API to retrieve some data about my cloud sync tasks, including the start date and end date. I'm a little befogged by the time stamps I'm seeing, though, and wanted to check if anyone had any insight. Here's an example json blob returned after calling /api/v2.0/cloudsync

Code:
{'id': 113,
 'description': 'PUSH my data',
 'direction': 'PUSH',

 # -- snip --

 'locked': False,
 'job': {'id': 1234,
  'method': 'cloudsync.sync',
  'arguments': [113],
  'logs_path': '/tmp/middlewared/jobs/4196.log',
  'logs_excerpt': '2022/06/17 00:00:04 INFO  : \nTransferred:   \t         0 / 0 Bytes, -, 0 Bytes/s, ETA -\nElapsed time:         1.0s\n\n2022/06/17 00:00:05 INFO  : \nTransferred:   \t         0 / 0 Bytes, -, 0 Bytes/s, ETA -\nChecks:                51 / 2341, 2%\nElapsed time:         2.0s\nChecking:\n * fils/a.bin: checking\n... 2783 more lines ...\n * : checking\n * files/n.bin: checking\n\n2022/06/17 00:03:24 INFO  : There was nothing to transfer\n',
  'progress': {'percent': 100,
   'description': 'checks: 19853 / 19853',
   'extra': None},
  'result': None,
  'error': None,
  'exception': None,
  'exc_info': None,
  'state': 'SUCCESS',
  'time_started': {'$date': 1655449200272},
  'time_finished': {'$date': 1655449404621}}}


What's the time format for 1655449200272 and 1655449404621? It doesn't seem to match the epoch, and the duration itself seems longer than the job actually took.
Thanks!
 
Top