> 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/cloud/da/concepts/intermediate-concepts/logs.md).

# Logge

Logge i Devolutions Cloud registrerer handlinger på postniveau og hændelser på tværs af systemet, samlet i Rapporter og klar til eksport til Azure Log Analytics til revisioner.

Logge registrerer detaljerede oplysninger om aktivitet i Devolutions Cloud, fra kommentarer og handlinger på postniveau til hændelser på tværs af systemet. På postniveau registrerer sektionen Logge brugerinteraktion som visninger, redigeringer og kommentarer og giver mulighed for eksport til yderligere analyse.

På rapportniveau samler visningen Logge under Rapporter aktivitetslogge, administrationslogge og brugerhandlinger på tværs af bokse og giver administratorer et centralt revisionsspor. Disse logge kan også videresendes til eksterne systemer som Azure Log Analytics til langtidsopbevaring og korrelation med anden sikkerhedstelemetri.

#### Relaterede emner

* [Logge](/cloud/da/web-interface/reports/logs.md)
* [Send logge fra Devolutions Cloud til Azure Log Analytics](/cloud/da/knowledge-base/how-to-articles/send-devolutions-cloud-logs-to-azure-log-analytics.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.devolutions.net/cloud/da/concepts/intermediate-concepts/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.