> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/5.1/support/diagnostics-management/traces-management/manage-traces-using-the-cli.md).

# Manage traces using the CLI

Manage trace settings using the CLI commands:

* Initiate trace collection
* Stop trace collection
* View traces configuration status
* Modify traces retention settings
* Adjust traces verbosity level to high or low
* Manage the traces freeze period

## Initiate trace collection

**Command:** `weka debug traces start`

## Stop trace collection

**Command:** `weka debug traces stop`

## View traces configuration status

**Command:** `weka debug traces status`

## Modify traces retention settings

**Command:** `weka debug traces retention set [--server-max server-max] [--client-max client-max] [--server-ensure-free server-ensure-free] [--client-ensure-free client-ensure-free]`

**Parameters**

<table><thead><tr><th width="240">Parameter</th><th>Description</th><th>Default</th></tr></thead><tbody><tr><td><code>server-max</code></td><td>Maximum capacity to retain per server.</td><td>50 GB per IO-node, with a minimum of 100 GB for all IO-nodes.</td></tr><tr><td><code>client-max</code></td><td>Maximum capacity to retain per client.</td><td>50 GB per IO-node, with a minimum of 100 GB for all IO-nodes.</td></tr><tr><td><code>server-ensure-free</code></td><td>Always maintain at least this much capacity to remain free on servers.</td><td>3 GB</td></tr><tr><td><code>client-ensure-free</code></td><td>Always maintain at least this much capacity to remain free on clients.</td><td>3 GB</td></tr></tbody></table>

{% hint style="info" %}
To modify the trace retention setting of a single client, you can use the `traces_capacity_mb` mount command. See [Mount filesystems](/5.1/weka-filesystems-and-object-stores/mounting-filesystems.md#additional-mount-options-using-the-stateless-clients-feature).
{% endhint %}

### Restore default traces retention values

**Command:** `weka debug traces retention restore-default`

## Adjust traces verbosity level

**Command:** `weka debug traces level set <level>`

**Parameters**

<table><thead><tr><th width="161">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>level</code>*</td><td><p>Verbosity level.</p><p>Format: <code>low</code> or <code>high</code></p></td></tr></tbody></table>

## Manage the traces freeze period

### View the frozen trace period

**Command:** `weka debug traces freeze show`

### Set the freeze period

**Command:** `weka debug traces freeze set <comment> [--start-time start-time] [--end-time end-time] [--retention retention]`

**Parameters**

<table><thead><tr><th width="190">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>comment</code> *</td><td>A descriptive note providing context for easier tracking and review of debug traces.</td></tr><tr><td><code>start-time</code></td><td><p>The start time of the frozen period.</p><p>Format: 5m, -5m, -1d, -1w, 1:00, 01:00, 18:30, 18:30:07, 2018-12-31 10:00, 2018/12/31 10:00, 2018-12-31T10:00, 2019-Nov-17 11:11:00.309, 9:15Z, 10:00+2:00</p></td></tr><tr><td><code>end-time</code></td><td><p>The end time of the frozen period.</p><p>Format: 5m, -5m, -1d, -1w, 1:00, 01:00, 18:30, 18:30:07, 2018-12-31 10:00, 2018/12/31 10:00, 2018-12-31T10:00, 2019-Nov-17 11:11:00.309, 9:15Z, 10:00+2:00</p></td></tr><tr><td><code>retention</code></td><td><p>The time to retain the traces.</p><p>Format: 3s, 2h, 4m, 1d, 1d5h, 1w, infinite/unlimited</p></td></tr></tbody></table>

### Reset the traces freeze period and delete the existing frozen traces

**Command:** `weka debug traces freeze reset`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/5.1/support/diagnostics-management/traces-management/manage-traces-using-the-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.