> 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.2/support/diagnostics-management/protocols-debug-level-management.md).

# Protocols debug level management

This page describes the S3, NFS, and SMB protocols debug level management. A higher debug level provides more details for investigating issues.

The cluster enables changing the log debug level (verbosity level) for each protocol container in the cluster. While investigating issues, you can increase the verbosity level.

{% hint style="warning" %}
Do not change protocols debug level without specific instructions from the [Customer Success Team](/4.2/support/getting-support-for-your-weka-system.md#contact-customer-success-team). Changing the protocols debug level reduces the amount of troubleshooting information about the system and may affect the SLA if an issue occurs.
{% endhint %}

{% hint style="info" %}
Once the container is restarted, the log verbosity level reverts to its default.
{% endhint %}

**Related topics**

[Manage protocols debug level using the GUI](/4.2/support/diagnostics-management/protocols-debug-level-management/manage-protocols-debug-level-using-the-gui.md)

[Manage protocols debug level using the CLI](/4.2/support/diagnostics-management/protocols-debug-level-management/manage-protocols-debug-level-using-the-cli.md)


---

# 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/4.2/support/diagnostics-management/protocols-debug-level-management.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.