rpk debug remote-bundle start
Start a remote debug bundle collection in your cluster.
This command starts the debug collection process in a remote cluster that you configured in flags, environment variables, or your rpk profile.
After starting the debug collection process, you can query the status with
rpk debug remote-bundle status. When it completes, you can download it with
rpk debug remote-bundle download.
Use the flag --no-confirm to avoid the confirmation prompt.
Flags
| Value | Type | Description |
|---|---|---|
|
string |
The size limit of the controller logs that can be stored in the bundle. For example: 3MB, 1GiB. |
|
duration |
How long to collect samples for the CPU profiler. For example: 30s, 1.5m. Must be higher than 15s. |
|
string |
Custom UUID to assign to the job that generates the debug bundle. |
|
int |
The maximum number of Kafka connections to store in the bundle. |
|
stringArray |
Comma-separated label selectors to filter your resources. For example: <label>=<value>,<label>=<value> (K8s only). |
|
string |
Include logs dated from specified date onward; (journalctl date format: YYYY-MM-DD, |
|
string |
Read the logs until the given size is reached. For example: 3MB, 1GiB. |
|
string |
Include logs older than the specified date; (journalctl date format: YYYY-MM-DD, |
|
duration |
Interval between metrics snapshots. For example: 30s, 1.5m. |
|
int |
Number of metrics samples to take (at the interval of |
|
string |
The namespace to use to collect the resources from (K8s only). |
|
bool |
Disable confirmation prompt. |
|
stringArray |
Comma-separated partition IDs. When provided, |
|
bool |
Wait for completion of remote bundle before returning. |
|
duration |
How long to wait locally for remote-bundle completion if |
Global flags
| Value | Type | Description |
|---|---|---|
|
string |
Redpanda or |
|
stringArray |
Override |
|
bool |
Ignore |
|
string |
|
|
bool |
Enable verbose logging. |