Nutanix Collector¶
Clarity Transform imports a VMware estate from a Nutanix Collector export: virtual machines, hosts, clusters, datacentres, datastores, disks and networks, from a workbook rather than from a live connection.
Where to find it¶
Go to Discover → Integrations, then select the Nutanix Collector card. The card's category label is File. The integration's page has the Endpoints and History tabs; Integrations describes the page, its grid and its row actions.
Why we do this¶
A Nutanix Collector export is often already in hand at the start of a Nutanix-bound engagement, so the data has already been gathered and cleared.
Reading it means Clarity starts from the same source the sizing conversation started from, which avoids the awkward position of two tools describing the same estate differently because they were fed different exports.
What we collect¶
- Virtual machines, with their configuration and resource allocation
- Hosts, clusters and datacentres, with the placement relationships between them
- Datastores and virtual disks
- Network configuration
This is the integration to reach for when access is the blocker
It needs no account on any system, no inbound or outbound connectivity to an appliance, and no firewall change. Where a security review is holding up the credentialed integrations, this is a way to make progress in the meantime rather than waiting.
What it adds¶
Where a customer has already produced a Collector export for a sizing, using it is both faster and less contentious than asking for a second collection.
A file is a point in time
The export describes the estate on the day it was taken.
What is deliberately not inferred¶
- No traffic data.
- No application or role detection.
- Nothing is connected to and no credential is used.
- Placement is not a dependency. Two machines on the same host are not related by that fact alone.
What we require¶
No credential is used. This integration needs no account on any system, so there is nothing for a customer to provision and nothing to revoke afterwards.
Verification before handover¶
- Confirm the export covers the whole estate. The export reflects what the account running it could see.
- Confirm the expected sheets are present. Virtual machines, hosts, clusters, datacentres, datastores, disks and networks. A partial export imports what it has.
Configuring the endpoint¶
On the integration's Endpoints tab, select the add icon (Create New Integration Endpoints). The Create new entry form opens with these fields, in this order:
| Field | Value |
|---|---|
| Name | A name for the endpoint |
| File Upload | The Nutanix Collector export, chosen with Choose file... |
| Enabled | Ticked. The box is unticked when the form opens |
The endpoint form has no End Point, Credential or Job Schedule field, although the Endpoints grid has those columns.
No field is marked as required. Technology is set by the card and is hidden in the form. Select Save to create the endpoint, or Cancel to close the form. The edit icon opens the same fields as Edit entry.
When you choose the file, the form shows "File uploaded:" and the file name. After saving, the End Point column shows the file name, and View Details shows it under File Upload.
To import the file, select Mark as Running on the endpoint's row, then read Last Result and the History tab. There is no schedule, so the file is not read again unless you run the endpoint again.
Removing the access¶
There is nothing to remove.
Troubleshooting¶
| Symptom | Cause |
|---|---|
| Fewer virtual machines than expected | The account that ran the export could not see them all. |
| Some sheets missing from the import | The export does not contain them. |
| The data disagrees with a live hypervisor integration | The file is older. Prefer the live source where both exist. |
| Mark as Running is greyed out | Enabled is cleared, the endpoint has not been saved, or a run is still in progress. Tick Enabled, save, and wait for Last Result to show a finished run. |