> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/tutorials/inventory/collect_data.md).

# Collect Data

{% hint style="info" %}
**Information**

The GLPI Inventory plugin is available in the menu **`Administration`** > **`GLPI Inventory`**\
If it is not installed, please go to the **marketplace**, and install the GLPI Inventory plugin

\
![Alt text](/files/VhYBx7lSQbt4psi2zB2y)
{% endhint %}

## Declaration of a data to be queried

{% hint style="info" %}
**Information**

In the following example, we are going to check that the user has the thunderbird icon on his desktop (which in this case is a portable application).
{% endhint %}

Go to the **`administration`** > **`GLPI Inventory`** > **`tasks`** > **`computer information`**

<div align="left"><img src="/files/K49DMXYhsv88n4mTRj1F" alt=""></div>

Then create a new item **`ajouter`** :

![](/files/v5LyrwkGtuJ92FOlno9t)

The next window will allow you to enter the following information:

* A name
* A comment
* A type
  * Registry
  * [WMI](broken://spaces/QFOh36etagWOcP9q4ECb/pages/uyV7vc1BgpEAKyDInQFN#comment-configurer-la-collecte-wmi)
  * Search for a file
* Active or not
* Visible in a sub-entity or not

![](/files/BTV4y2a4UhhuTFvIt2bd)

Once you've clicked on **`Add`**, a **`Collect configuration`** tab appears in the left-hand menu, allowing you to configure data collection for one of the following three options, depending on the chosen type:

* WMI Windows
* File search
* Windows registry

![](/files/zV9NqbrrjNPDq3K2mS34)

## Creating the task

Go to **`administration`** > **`GLPI Inventory`** > **`tasks`** > **`task management`**

<div align="left"><img src="/files/P5NCyUopTcsJt9B6k1hW" alt=""></div>

Then create a new task with **`ajouter`** :

![](/files/2OimhIZKB5qLmAZafbEj)

Create the task :

![](/files/LpXeHLnKUVIl0QCADeDO)

Then in **`Job configuration`**, add a job:

![](/files/V9N36psTqm2yrwwOu3CE)

And configure the collect job in this task:

![](/files/zFtCPaFQtUt12AuHxZeP)

Once the job has been activated, prepared and taken over by the agent, you can see the result of the job execution here:

![](/files/Q9FzHq5HuMr5ulvYo0ct)

In the computer file, a new tab **`Collection information`** appears with the value found for the file:

<div align="left"><img src="/files/J36vYnGMW9byDyLzNhyS" alt=""></div>

![](/files/uoOGSwgWuypPrwGIN9N4)


---

# 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, and the optional `goal` query parameter:

```
GET https://help.glpi-project.org/tutorials/inventory/collect_data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
