> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-user-manual/analytics/device-events.md).

# Device Events

Device events are events that are specific to individual devices, and are logged to EnGenius Cloud. Examples of events would include the specific time that a device comes online or goes offline.

Use this screen to view **Device Events.**  

Click **Analyze** > **Event Log** > **Device Event** to access this screen.

![](https://3893603398-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LgVsoqihVR3I0VRYmyO%2F-Lo-HbDQzQtLd1cl5SS2%2F-Lo-Hf4yADyxBsrrz6-E%2F1567667123157.jpg?alt=media\&token=cc377db1-0835-4d04-b060-a489b64d959f)

## Searching the Event Log

EnGenius Cloud allows to search device events based on a number of desired parameters. 

![](https://3893603398-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LgVsoqihVR3I0VRYmyO%2F-Lo-HLZ_zD2yqo4f9dIe%2F-Lo-HZu_JNLT3GJ3Kl-h%2F1567667193225.jpg?alt=media\&token=880ff806-9b69-4649-91e2-27b11e44e3d6)

You can specify date/time, severity, and other parameters. Select one or multiple **event types**, then enter the **SSID**, **device name/MAC**, or select **client** to display the log messages related to it. After customizing your search parameters, remember to click **Apply** to perform the search.


---

# 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://doc.engenius.ai/home-cloud-user-manual/analytics/device-events.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.