Enhance the utility of MMTC's CLI for existing automation by improving its reporting of status on exit:
- Adding additional exit codes to convey meaning for success or lack thereof (i.e. distinguish between 'no valid telemetry within query window' and other types of errors)
Consider also:
- Enhancing the Run History File to include information about executions that did not complete successfully, including a JSON object containing structured information about the run
- Optionally writing the aforementioned JSON file to stdout & the log file
Enhance the utility of MMTC's CLI for existing automation by improving its reporting of status on exit:
Consider also: