> 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/infraon-configuration/it-operations/discovery/hypervisor-monitoring.md).

# Hypervisor Monitoring

Streamline device credential management and seamless VMware integration. Create device credentials, select HTTP with name and password, then discover and connect to VMware. Easily view assets through IT assets virtualization.&#x20;

## **Hypervisor Host**&#x20;

Discover detailed information about individual physical hosts, VM inventory, and resource allocation. View VM names, IP addresses, device details, and cluster status. The intuitive Timeline feature gives valuable insights into CPU, memory, storage, and VM states. Uncover data store capacity, VM allocation, and host connectivity. Explore device and storage resources for optimized host management.&#x20;

## **Hypervisor cluster**&#x20;

Seamlessly manage host clusters with comprehensive CPU, memory, and storage information: track VM and host details within the cluster. Monitor storage allocation, create VM templates, and adjust resources as needed. Explore host, VM, datastore, and resource insights for seamless cluster administrator.&#x20;


---

# 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.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/hypervisor-monitoring.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.
