> 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/4.0/support/diagnostics-management/protocols-debug-level-management/manage-protocols-debug-level-using-the-gui.md).
# Manage protocols debug level using the GUI
The Protocols Debug Level section displays the debug level for the S3 and NFS protocols only (the SMB debug level is not shown). You can change the debug level only for the configured protocols.
Using the GUI, you can:
* [Update S3 debug level](#update-s3-debug-level)
* [Update NFS debug level](#update-nfs-debug-level)
* [Update SMB debug level](#update-smb-debug-level)
{% hint style="info" %}
Once the container is restarted, the log verbosity level reverts to its default.
{% endhint %}
## Update S3 debug level
If the S3 protocol is configured, you can change the debug level for all hosts or specified hosts.
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**.
2. From the left pane, select **Support**.
3. On the Protocols Debug Level section, select **Change S3 debug level**.
4. On the Update S3 Debug Level dialog, set the following properties:
* **Level:** Select the debug level.
* **All members:** If you want to apply the update on all the hosts, switch to **On**. If you want to apply the update on specific hosts, switch to **Off** and select the required hosts.
## Update NFS debug level
If the NFS protocol is configured, you can change the debug level for all hosts or specified hosts.
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**.
2. From the left pane, select **Support**.
3. On the Protocols Debug Level section, select **Change NFS debug level**.
4. On the Update NFS Debug Level dialog, set the following properties:
* **Level:** Select the debug level.
* **All members:** If you want to apply the update on all the hosts, switch to **On**. If you want to apply the update on specific hosts, switch to **Off** and select the required hosts.
## Update SMB debug level
If the SMB protocol is configured, you can change the debug level for all hosts or specified hosts.
The available debug levels are:
* 0 - NO DEBUG
* 5 - MID DEBUG
* 10 - FULL DEBUG
**Procedure**
1. From the menu, select **Configure > Cluster Settings**.
2. From the left pane, select **Support**.
3. On the Protocols Debug Level section, select **Change SMB debug level**.
4. On the Update SMB Debug Level dialog, set the following properties:
* **Level:** Select the debug level.
* **All members:** If you want to apply the update on all the hosts, switch to **On**. If you want to apply the update on specific hosts, switch to **Off** and select the required hosts.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.weka.io/4.0/support/diagnostics-management/protocols-debug-level-management/manage-protocols-debug-level-using-the-gui.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.