> 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/6.0/support/diagnostics-management/traces-and-protocols-debug-level-management/manage-traces-and-protocols-debug-level-using-the-gui.md).

# Manage traces and protocols debug level using the GUI

Control trace collection, verbosity level, freeze periods, default settings, and protocols debug levels using the GUI.

Manage trace collection and protocol debug levels from **Configure > Cluster Settings > Support**. The screen includes the **Traces** and **Protocols Debug Level** sections.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-a3fb8f8c8ccf21f0e8d6ff7aa5e6afe79875ac43%2Fsupport_traces_protocols_debug.png?alt=media" alt=""><figcaption><p>Support settings</p></figcaption></figure></div>

## Traces

The Traces section displays the current traces status, ensured free capacity and maximum traces size for backends and clients, verbosity level, and freeze period.

To modify the maximum traces size and the ensured free capacity, use the CLI. See Manage traces and protocols debug level using the CLI.

### Disable traces

Disable traces to stop collecting tracing data on the cluster.

{% hint style="warning" %}
Do not disable traces without specific instructions from the Customer Success Team. Disabling traces reduces the troubleshooting information about the system and may affect the SLA if an issue occurs.
{% endhint %}

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Traces section, select **Disable traces**. Then, in the confirmation message, select **Yes**.

To resume trace collection, select **Enable traces**.

### Change traces verbosity level

The verbosity level determines the amount of information in the tracing data. Setting the verbosity level to high provides more troubleshooting detail but can consume more disk space.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-f65a1d09032e216e41f9ea40e5a2b416b08863ba%2Ftraces_change_verbosity.png?alt=media" alt="" width="563"><figcaption><p>Change traces verbosity level</p></figcaption></figure></div>

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Traces section, depending on the current verbosity level (low or high), select **Change traces level to high** or **Change traces level to low**.

### Freeze traces

Freeze traces for a selected period to retain data for investigation.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-a1b0d760077607410d4659c07df6d6d93bc59850%2Ffreeze_traces.png?alt=media" alt="" width="563"><figcaption><p>Freeze traces</p></figcaption></figure></div>

**Before you begin**

Identify the trace period and its required retention time.

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Traces section, select **Freeze traces**.
3. In the **Freeze traces** dialog, set the following properties:
   * **Start:** Set the start date and time of the trace period.
   * **End:** Set the end date and time of the trace period.
   * **Retention:** Set the retention period and its unit, for example, days.
   * **Override:** Turn on to replace an existing freeze period.
4. Select **Save**.

The Traces section displays the freeze start time, freeze end time, and the date until which the traces are retained.

### Reset traces freeze

Clear the freeze period when the investigation is complete. The traces return to the standard rotation.

{% hint style="warning" %}
Resetting the freeze period deletes the existing frozen traces.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-77132833c0f853caf510553ceed3641dd421988f%2Ffreeze_traces_result.png?alt=media" alt=""><figcaption><p>Reset traces freeze</p></figcaption></figure></div>

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Traces section, select **Reset traces freeze**. Then, in the confirmation message, select **Yes**.

### Restore traces default settings

Restore the traces configuration to its default settings.

{% hint style="info" %}
The default maximum traces capacity is 50 GiB per I/O process, with a minimum of 100 GiB and a maximum of 1000 GiB per server. The default minimum free capacity is 3 GiB.
{% endhint %}

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Traces section, select **Restore traces default settings**. Then, in the confirmation message, select **Yes**.

## Protocols debug level

The Protocols Debug Level section displays the debug level for the S3, NFS, and SMB protocols. If a protocol is not configured, the section indicates it, and you cannot change its debug level.

{% hint style="info" %}
After the protocol container restarts, the debug level reverts to its default.
{% endhint %}

### Change S3 debug level

If the S3 protocol is configured, you can change the debug level for all servers or specified servers.

The available debug levels are:

* 0 - CRITICAL
* 1 - ERROR
* 2 - WARNING
* 3 - INFO
* 4 - DEBUG
* 5 - TRACE

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Protocols Debug Level section, select **Change S3 debug level**.
3. In the **Update S3 Debug Level** dialog, set the following properties:
   * **Level:** Select the debug level.
   * **All servers:** To apply the update to all servers, switch to **On**. To apply the update to specific servers, switch to **Off** and select the required servers.
4. Select **Save**.
5. In the **Confirm S3 debug level change** message, select **Yes**.

### Change NFS debug level

If the NFS protocol is configured, you can change the debug level for all servers or specified servers.

The available debug levels are:

* 1 - EVENT
* 2 - INFO
* 3 - DEBUG
* 4 - MID DEBUG
* 5 - FULL DEBUG

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Protocols Debug Level section, select **Change NFS debug level**.
3. In the **Update NFS Debug Level** dialog, set the following properties:
   * **Level:** Select the debug level.
   * **All servers:** To apply the update to all servers, switch to **On**. To apply the update to specific servers, switch to **Off** and select the required servers.
4. Select **Save**.
5. In the **Confirm NFS debug level change** message, select **Yes**.

### Change SMB debug level

If the SMB protocol is configured, you can change the debug level for all servers or specified servers.

The available debug levels are:

* 0 - NO DEBUG
* 5 - MID DEBUG
* 10 - FULL DEBUG

**Procedure**

1. From the menu, select **Configure > Cluster Settings**, and select the **Support** tab.
2. In the Protocols Debug Level section, select **Change SMB debug level**.
3. In the **Update SMB Debug Level** dialog, set the following properties:
   * **Level:** Select the debug level.
   * **All servers:** To apply the update to all servers, switch to **On**. To apply the update to specific servers, switch to **Off** and select the required servers.
4. Select **Save**.
5. In the **Confirm SMB debug level change** message, select **Yes**.


---

# 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/6.0/support/diagnostics-management/traces-and-protocols-debug-level-management/manage-traces-and-protocols-debug-level-using-the-gui.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.
