> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/faqs-platform/events.md).

# Events

**Q:** What are the Events?\
**A:** Events are records of actions or conditions triggered by devices or platform configurations. They provide a detailed timeline of activities, such as alarms, warnings, or operational updates, allowing users to monitor and analyze device behavior.

***

**Q:** How do I communicate that I solved an event type?\
**A:** To mark an event as resolved, navigate to the event details and click on the "Resolved" button. This action indicates that the issue related to the event has been addressed.

***

**Q:** How can I communicate that I took charge of an event?\
**A:** To take charge of an event, open the event details and click on the "Confirm" button. This signifies that the event is being actively handled by a user.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.g-iot.io/faqs-platform/events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.