> 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/server/web-interface/vaults/entries/entry-section/logs.md).

# Logs

The Logs tab on a Devolutions Server entry displays user interaction history and lets users insert log comments with tickets, dates, and notes.

Consult ***Logs*** and ***Insert log comments*** specific to entries about user interaction. To view the ***General***, ***Details*** and ***Comments*** of a specific log, click the ***Log Entry*** button and click the ***Export*** button to generate a CSV file.

#### Insert an entry log comment

{% hint style="warning" %}
***Log Comments*** for entries in the Devolutions Server web interface can only be viewed. They cannot be deleted nor edited once saved. More options, like notes editing, are available in Remote Desktop Manager.
{% endhint %}

1. Click ***Logs*** in an entry.
2. Click the ***Insert Log Comment*** button.
3. The ***Name*** of the log cannot be edited, it is by default the entry ***Name***.
4. Optional: Add a ***Ticket*** number.
5. Optional: To select an ***End Date***, check the ***End*** box and select an end date to the log.
6. Insert a ***Message*** for the log.

{% hint style="warning" %}
Only the ***Message*** text will be exported and showed in preview mode for entries.
{% endhint %}

7. Optional: Add more detailed information about the log in the ***Notes*** text box.
8. Click ***OK***.


---

# 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/server/web-interface/vaults/entries/entry-section/logs.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.