GLOBUS TASK EVENT-LIST
SYNOPSIS
globus task event-list [OPTIONS] TASK_ID
globus task event-list --filter-errors [OPTIONS] TASK_ID
globus task event-list --filter-non-errors [OPTIONS] TASK_ID
DESCRIPTION
This command shows the recent events for a running task. Most events of interest are fault events, which are errors which occurred on an endpoint but which are non-fatal to a task. For example, Permission Denied errors on an endpoint don’t cancel the task because they are often resolvable — at which point the task would retry succeed.
Events may be filtered using '--filter-errors' or '--filter-non-errors', but these two options may not be used in tandem.
OPTIONS
-
--limit
INTEGER
-
Limit number of results. [default: 10]
- --filter-errors
-
Filter results to errors
- --filter-non-errors
-
Filter results to non errors
- -v, --verbose
-
Control level of output, make it more verbose.
- --quiet
-
Suppress non-essential output. This is higher precedence than
--verbose
. - -h, --help
-
Show this message and exit.
-
-F, --format
[unix|json|text]
-
Output format for stdout. Defaults to text.
-
--jmespath, --jq
TEXT
-
A JMESPath expression to apply to json output. Forces the format to be json processed by this expression.
-
--map-http-status
TEXT
-
Map HTTP statuses to any of these exit codes: 0,1,50-99. e.g. "404=50,403=51"
OUTPUT
When output is in text mode, the following fields are used:
-
'Time'
-
'Code'
-
'Is Error'
-
'Details'
EXAMPLES
Show why a task is paused, producing JSON output:
$ globus task pause-info TASK_ID --format JSON
EXIT STATUS
0 on success.
1 if a network or server error occurred, unless --map-http-status has been used to change exit behavior on http error codes.
2 if the command was used improperly.
3 if the command was used on the wrong type of object, e.g. a collection command used on an endpoint.
4 if the command has authentication or authorization requirements which were not met, as in ConsentRequired errors or missing logins.