> 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/fr/knowledge-base/how-to-articles/verbose-logs-level-in-ssh-shell.md).

# Niveau de journalisation détaillé dans SSH Shell

Comprenez les niveaux de journaux détaillés disponibles pour les sessions SSH Shell dans Remote Desktop Manager lors du dépannage de problèmes de connexion.

Lorsqu'un problème survient avec une session SSH Shell, le soutien technique pourrait vous demander de lui envoyer un ***journal détaillé***. Différents niveaux de détail existent :

* Niveau 1 : Information sur les traces de la connexion.
* Niveau 2 : Information sur les traces de la connexion et débogage plus approfondi.
* Niveau 3 : Information sur les traces de la connexion, débogage plus approfondi et débogage des messages d'erreur courants.
* Niveau 4 : Information sur les traces de la connexion, débogage plus approfondi, débogage des messages d'erreur courants et détails pour chaque paquet transmis.

En général, nous exigerons un ***journal détaillé*** réglé au niveau 2.

### Voir aussi

* [Journaux détaillés du terminal 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/fr/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.