> 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/journey-to-getting-started-with-giot/18.-generating-reports.md).

# 18. Generating Reports

## **Understand how to generate and dowload data reports.**

Creating reports on GIoT involves exporting data directly from various sections of the platform, such as devices, alarms, events, or device lists with a specif battery level. These exports allow users to analyze data in external tools. Follow these general steps:

* **Use Filters to Narrow Data:** Apply filters in the desired section (e.g., Devices, Alarms, or Events) to focus on specific criteria, such as device type, status, or date range.
* **Export the Data:** Click on the export icon (usually available in the top-right corner) to download the filtered data. Choose the format, such as **CSV** or **JSON**.
* **Customize the Output:** Use the platform's flexible filtering options to tailor the exported data to your needs, ensuring only relevant information is included.

<figure><img src="https://122097802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfEQ6KpTjmszWVWQqgcEa%2Fuploads%2FlJaWkGdC0dcyBkJiMGtt%2Fimage.png?alt=media&amp;token=97633d92-593c-4f25-8f43-70f1803bf5f3" alt=""><figcaption></figcaption></figure>


---

# 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.g-iot.io/journey-to-getting-started-with-giot/18.-generating-reports.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.