> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/it/knowledge-base/how-to-articles/verbose-logs-level-in-ssh-shell.md).

# Livello di log verbose in SSH Shell

Comprenda i livelli di log verbose disponibili per le sessioni SSH Shell in Remote Desktop Manager durante la risoluzione dei problemi di connessione.

Quando si verifica un problema con una sessione SSH Shell, il supporto potrebbe richiederle di inviare un ***Verbose log*** Esistono diversi livelli di verbose:

* Livello 1: Informazioni sulle tracce della connessione.
* Livello 2: Informazioni sulle tracce della connessione e debug più approfondito.
* Livello 3: Informazioni sulle tracce della connessione, debug più approfondito e debug dei messaggi di errore comuni.
* Livello 4: Informazioni sulle tracce della connessione, debug più approfondito, debug dei messaggi di errore comuni e verbose per ogni pacchetto trasmesso.

In generale richiederemo un ***Verbose log*** impostato sul livello 2.

### Vedere anche

* [Log verbose del terminale SSH](https://academy.devolutions.net/student/page/2493255-ssh-terminal-verbose-logs?sid=382b1415-4f21-44b8-82d7-4443e98dd5cb\&sid_i=0)


---

# 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.devolutions.net/rdm/it/knowledge-base/how-to-articles/verbose-logs-level-in-ssh-shell.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.
