Diagnostics Command Reference
Contents
Diagnostics Command Reference#
Use the diagnostics tool to log resource usage on a Duckietown device and push the results to the cloud for analysis.
Syntax#
dts diagnostics run \
[-H ROBOT] \ # where the tool itself runs
-G EXPERIMENT \ # experiment name
-d SECONDS \ # capture length
[OPTIONS]
Legacy options#
Argument |
Default |
Description |
|---|---|---|
|
|
Docker socket or hostname where to run the diagnostics image. This is not the monitored target. |
|
|
Docker endpoint to monitor. |
|
|
Specify a device type (e.g., |
|
Automatic |
ID of the API App used to authenticate the upload to the server. Must have access to the |
|
Automatic |
Secret of the API App used to authenticate the upload to the server. |
|
|
Name of the logging database. Must be an existing database. |
|
Required |
Name of the experiment (e.g., |
|
|
Name of the test within the experiment (e.g., |
|
Required |
Length of the analysis in seconds. Use |
|
|
Specify regular expressions used to filter the monitored containers. |
|
|
Log system processes as well. |
|
|
Custom notes to attach to the log. |
|
|
Do not pull the diagnostics image before running the experiment. |
|
|
Run in debug mode. |
|
|
Run in verbose mode. |
|
|
Do not upload the statistics to the Duckietown server. |