Agentless monitoring for Nutanix infrastructure through the Prism API. Discover and monitor clusters, hosts, virtual machines, and storage containers, and collect alerts and events raised by Nutanix Prism.
Cloudmon Nutanix monitoring connects to Nutanix Prism through its native API and discovers the resources managed by that instance, requiring no agent installation on the cluster, the hosts, or the virtual machines. A single connection to Prism Central or Prism Element gives Cloudmon visibility across every resource under that instance.
Supported entity types are Nutanix Prism, Nutanix Cluster, Nutanix Host, Nutanix VM, and Nutanix Storage Container. All discovered entities are accessible under Virtualization → Nutanix in the Cloudmon navigation bar, each with its own dashboard and monitor list.
In addition to metric collection, Cloudmon can retrieve the alerts and events that Nutanix Prism raises internally, and optionally convert those alerts into Cloudmon alarms that clear themselves when Nutanix resolves the underlying condition. This means a Nutanix-detected problem surfaces in the same alarm workflow as the rest of the monitored environment.
Nutanix monitoring requires a Cloudmon probe that can reach the Prism instance over the network, and a Prism account with permission to read cluster, host, virtual machine, and storage container information. The Prism API is served on port 9440 by default, so the probe must be able to reach the Prism address on that port.
Credentials are entered directly on the monitor rather than being created in advance under Settings, so no separate credential record is required before adding the monitor.
Navigate to Virtualization → Nutanix → Nutanix Prism and click the Add button. The Add Nutanix Prism form is divided into four sections. Fill in the fields as follows, then click Save.
Basic identification and connection credentials.
| Field | Description |
| Probe* | The probe that connects to Prism and collects the data. Select a probe that can reach the Prism address on the Prism API port. |
| Display Name* | A display name for this Nutanix monitor, such as "Production Prism Central" or "Nutanix PE". |
| Prism Central / Prism Element URL* | The address of the Prism Central or Prism Element instance, including the port. The default Prism port is 9440, giving an address in the form https://prism.example.local:9440. |
| Allow Self-Signed TLS Certificates (Insecure TLS) | Enabled by default. Allows the connection to proceed when Prism presents a self-signed certificate, which is common on default Nutanix deployments. Disable this when Prism uses a certificate issued by a trusted certificate authority. |
| Username* | The Prism account Cloudmon authenticates with. |
| Password* | The password for the Prism account. |
Services, intervals, events, alerts, and notification.
| Field | Description |
| Resources to Discover* | The Nutanix resource types Cloudmon discovers and monitors from this Prism instance. Select only the resource types required to keep the monitored inventory focused. |
| Discovery Interval* | How often Cloudmon re-scans Prism for resources that have been added or removed. The default is 6 Hours. |
| Collect Nutanix Alerts | Enabled by default. Retrieves the alerts raised by Nutanix Prism so they are visible in Cloudmon. |
| Nutanix Alert Collection Interval* | How often Cloudmon retrieves alerts from Prism. The default is 5 Minutes. This field is available when Collect Nutanix Alerts is enabled. |
| Create Alarms based on Nutanix Alerts | Disabled by default. Automatically raises a Cloudmon alarm when Nutanix Prism reports an alert, and clears that alarm automatically once Nutanix resolves the alert. |
| Collect Nutanix Events | Disabled by default. Retrieves the events recorded by Nutanix Prism, giving a record of activity on the cluster alongside the alert stream. |
| Notify When New Resources Are Discovered | Disabled by default. Sends an alert when a discovery cycle finds a resource that was not previously monitored. |
Resource lifecycle and alert suppression settings. These control what Cloudmon does when a monitored resource is terminated or deleted in Nutanix.
| Field | Description |
| Keep Monitoring Terminated Resources | Disabled by default. Continues monitoring resources that have been terminated in Nutanix, retaining their historical data in Cloudmon. |
| Suppress Alerts for Deleted Resources | Disabled by default. Prevents alerts being raised for resources that have been deleted, which avoids alarm noise during planned decommissioning. |
| Automatically Remove Deleted Resources | Disabled by default. Deletes the Cloudmon monitor when the corresponding resource no longer exists in Nutanix. |
Groups and tags.
| Field | Description |
| Groups | Assign the monitor to logical groups for organised filtering and management. |
| User Groups | The user groups that should be notified for this Prism connection. |
| Third Party Services | Third-party integrations (such as Slack, Teams, or ITSM tools) to notify for this Prism connection. |
| Tags | Custom labels applied to the monitor for filtering across large environments. |
Note: The Nutanix Prism monitor has no alarm rule configuration. Prism is a collection point that pulls alerts directly from Nutanix and displays them. Alarm rules are configured on the individual Nutanix resources instead, such as clusters, hosts, virtual machines, and storage containers.
Click Save. Cloudmon connects to Prism and runs an initial discovery. Discovered resources appear under their respective entity pages in Virtualization → Nutanix.
Nutanix Prism raises its own alerts and records its own events independently of Cloudmon. Cloudmon retrieves both, which means conditions detected by Nutanix are visible in Cloudmon without needing a separate Prism session. Collected alerts and events are shown on the Alerts and Events tabs of the Nutanix Prism monitor.
Alerts are collected by default, on the interval set in Nutanix Alert Collection Interval. Collecting alerts makes them visible in Cloudmon but does not by itself raise a Cloudmon alarm. To have Nutanix alerts drive the Cloudmon alarm workflow, enable Create Alarms based on Nutanix Alerts. With that enabled, a Cloudmon alarm is raised when Prism reports an alert and is cleared automatically when Prism resolves it, so no manual closure is required.
Events are not collected by default. Enable Collect Nutanix Events to retrieve the activity record from Prism. Events describe activity on the cluster rather than fault conditions, so they provide context when investigating an alert rather than being an alerting source themselves.
Nutanix classifies its alerts as Critical, Warning, or Info. These are Nutanix severities carried through as reported by Prism, and are separate from the Cloudmon alarm severities of Critical, Trouble, and Attention that apply to alarms raised by Cloudmon alarm rules.
Both settings are configured per monitor in the Discovery Settings section, and can be changed at any time by editing the Nutanix Prism monitor.
Alarms can be configured for individual Nutanix clusters, hosts, virtual machines, and storage containers, or at the group level for all Nutanix entities of the same type. The Nutanix Prism connection itself has no alarm configuration, because it relays alerts that Nutanix has already raised rather than evaluating a threshold. Alerts arriving from Nutanix are controlled by the Create Alarms based on Nutanix Alerts setting on the Prism monitor. Each alarm is built around a simple IF/THEN model, where you select a metric, set a threshold, and define what happens when it is breached. Learn more.
For custom reports on Nutanix data, navigate to Reports → Custom Report and select the relevant Nutanix entity type. Reports can be delivered on a schedule and cover any metric collected against the selected entity. Learn more.
| Issue | What to check |
| Connection fails immediately after the monitor is added | Confirm the Prism URL includes the port. Prism serves its API on port 9440 by default, and an address entered without the port will fail to connect. Verify the selected probe can reach the Prism address on that port and that no firewall rule blocks it. |
| Connection fails with a certificate or TLS error | Nutanix deployments commonly present a self-signed certificate on Prism. Confirm Allow Self-Signed TLS Certificates is enabled on the monitor. If Prism has been configured with a certificate from a trusted certificate authority, disable that option and verify the full certificate chain is installed on Prism. |
| Authentication fails despite correct credentials | Confirm the Prism account has permission to read cluster, host, virtual machine, and storage container information. An account that can sign in to the Prism console may still lack the API read permissions required for discovery. |
| Some resource types are missing from the entity pages | Check the Resources to Discover selection on the monitor. Only the resource types selected there are discovered. After changing the selection, wait for the next discovery cycle or trigger a rediscovery from the Actions column on the Nutanix Prism page. |
| A newly created VM has not appeared in Cloudmon | Discovery runs on the Discovery Interval, which defaults to 6 Hours, so a resource created since the last cycle will not yet be present. Trigger a rediscovery from the Actions column, or reduce the Discovery Interval in environments where resources are created frequently. |
| Nutanix alerts are visible but no Cloudmon alarms are raised | Collecting alerts and raising alarms are separate settings. Collect Nutanix Alerts makes the alerts visible; Create Alarms based on Nutanix Alerts is what turns them into Cloudmon alarms. Enable the second setting on the monitor. |
| No alarms are raised even though metrics are being collected | Alarm rules are attached to the individual Nutanix resources, not to the Prism connection, so check the cluster, host, virtual machine, or storage container rather than the Prism monitor. Metric collection and alarming are separate: Cloudmon collects and charts the metrics regardless, but raises an alarm only where a rule has been applied. |
| Deleted virtual machines still appear as monitors | Cloudmon retains monitors for removed resources unless told otherwise. Enable Automatically Remove Deleted Resources in Resource Management to have those monitors deleted, and Suppress Alerts for Deleted Resources to stop them alerting in the meantime. |