JSON Backup Report Variables

Hey there,

I might’ve just failed to find it but is there documentation for all the variables that can be used in the JSON Backup Report. Can it be safely assumed that every JSON field is the equivalent of the variable name?

Right, you can use any keys listed in the default report:

{
  "computer": "mac-mini",
  "directory": "/Users/gchen/repository",
  "end_time": 1580837217,
  "new_chunk_size": 0,
  "new_chunks": 0,
  "new_file_chunk_size": 0,
  "new_file_chunks": 0,
  "new_file_size": 0,
  "new_files": 0,
  "new_metadata_chunk_size": 0,
  "new_metadata_chunks": 0,
  "result": "Error",
  "start_time": 1580837217,
  "storage": "local.storage",
  "storage_url": "/Users/gchen/storage",
  "total_chunk_size": 0,
  "total_chunks": 0,
  "total_file_chunk_size": 0,
  "total_file_chunks": 0,
  "total_file_size": 0,
  "total_files": 0,
  "total_metadata_chunk_size": 0,
  "total_metadata_chunks": 0,
  "upload_chunk_size": 0,
  "upload_file_chunk_size": 0,
  "upload_metadata_chunk_size": 0
}
1 Like

Since Duplicacy Web is not open source:

  1. What are all possible values for result?

  2. Is it safe to assume that any code that calls LOG_ERROR or LOG_FATAL will cause result to be “Error”?

  3. result will still be “Success” if LOG_WARN is called, which is not ideal when determining if a log was successful with no warnings. Is possible to implement any of the following:

  • Set result to “Warn” (or similar) if LOG_WARN is called; or
  • Add a new field “warning_count” (or similar) showing how many times LOG_WARN was called

The result can be Success, Failed, or Error. Failed means the job was terminated or a command-line option was invalid. Error means the job was aborted due to an error during execution.

Correct.

I’ll add a feature that lets you parse the log file using your own script.