> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/asset.md).

# Asset

The CMDB part of ITSM is incorporated as Assets within Infraon. Infraon Assets allows administrators/asset managers to view and manage all organizational assets, i.e., all IT and non-IT assets, in one place.

Any device with an IP is known as an IT Asset or Node. It can be a Server, Router, Storage Device, Transport Device, Wireless controller, Access point, etc.; as part of an Asset, Infraon collects and maintains the complete inventory details for an asset. 

Infraon collects basic yet important inventory information for each device, server, hypervisor, and application. The inventory information includes: 

* IP Address  
* Hostname  
* Device Type  
* Vendor  
* Model  
* Serial Number  
* Operating System and Version  
* MAC Address  
* CPU Information  
* Memory  
* HDD Details  
* Port Level information 

Etc.,  

* For Hypervisors,  
* CPU Socket  
* No of Processor  
* CPU Speed  
* Hyper-Threading  
* Memory Size  

Etc.,  


---

# 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://docs.infraon.io/infinity/user-guide/asset.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.