> 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/concepts/advanced-concepts/events.md). # Events Monitor Devolutions Cloud events such as logins, entry changes, and PAM actions through Activity Logs and audit tools. Events are discrete actions or changes in Devolutions Cloud that are recorded for auditing, troubleshooting, and automation. They include activities such as user logins, entry creation and modification, permission changes, vault operations, and PAM-related actions, all surfaced in Reports – Logs through Activity Logs, User Activity, and Administration Logs. These events feed the Audit tools, such as the entry security analyzer and password analyzer, and can be streamed to external systems via webhooks or Azure Log Analytics for SIEM correlation. A security team might, for example, investigate an unusual login or mass permission change by combining Devolutions Cloud events with alerts in their monitoring platform. #### Related topics * [Logs](/cloud/web-interface/reports/logs.md) * [Audit](/cloud/web-interface/reports/audit.md) * [Send Devolutions Cloud logs to Azure Log Analytics](/cloud/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/concepts/advanced-concepts/events.md?ask=&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.