Usage: getlogs [OPTIONS]
         Downloads logs from the log manager running in the cluster. The command requires a container name,
         a time range or both to limit the number of log entries to be downloaded
 
   OPTIONS:
        -c <containerName>      : Get logs for a container. Can request logs for multiple containers with multiple -c options.
                                  The container names in a pod can be found by running:
                                  "kubectl get pod <yourPodID> -o jsonpath={.spec.containers[*].name}"
        -p <numHours>           : Request logs for past number of hours
        -f <timestamp>          : From timestamp (iso-8601 formatted from timestamp e.g. 2018-05-04T20:40:03)
        -t <timestamp>          : To timestamp (iso-8601 formatted to timestamp e.g. 2018-05-04T21:40:03)
        -l <level>              : Filter on the given log level. Valid options TRACE/WARN/WARNING/ERROR/DEBUG/FINE/FINER/FINEST/AUDIT-SEC
        -F <outputFormat>       : Choose the log output format: json or short. defaults to json
        -o <outFileName>        : Name of the output tar file. Defaults to log-`date`.tgz. If the file name
                                  does not include path, the output file will be placed in /var/avaya/artifactCache directory
        -D <outputDirectory>    : Name of the directory where the downloaded logs (chunks of 10k records) will be placed.
                                  If this directory is specified the downloaded logs will not be tarred, unless -o option is also specified.
                                  If the output file name is specified with -o option and the name contains path to the destination file,
                                  the path of the file name is ignored and the directory specified via this option is used.
                                  The outputDirectoy specified in this option should not exist.
       -h|--help                : Print this help message