> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/computers/computer-details/alerts.md). # Alerts Tab **Alerts** displays events related to the selected computer that may require administrator attention. ### Severity levels Alerts are divided into three levels: | Level | Meaning | | --------------- | --------------------------------------------------------------------- | | **Critical** | Events with the highest priority that may require immediate response. | | **Warnings** | Events indicating an issue or risk. | | **Information** | Informational events that may not require action. | ### Alert list The following may be displayed for each alert: * severity level, * event type, * description, * impact on the device, * date and time of occurrence, * current status.
podsumowanie i lista alertów
--- # 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/computers/computer-details/alerts.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.