---
sourceDocument: Zurich IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Nutanix Acropolis

# Nutanix Acropolis discovery {#ariaid-title1}

Release version: Zurich  
Updated June 3, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 9 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Nutanix Acropolis discovery

The ServiceNow Discovery application enables comprehensive discovery of Nutanix Acropolis components, including Nutanix Prism Central (version 2024.3.1.8 or higher) and Prism Element (7.0.1.6 or higher).
It leverages the Nutanix Components pattern, which uses REST APIs to gather detailed information about the Acropolis deployment.
Support for Nutanix API v4 discovery was introduced starting with Discovery and Service Mapping Patterns version 1.29.0, allowing discovery of new pool and container records while existing ones from earlier API versions become inactive.
Show full answer Show less  
In addition to discovery, Nutanix VM and Host Event patterns detect state changes in virtual machines and hosts, triggering rediscovery as needed. These event patterns run every five minutes but require manual activation of their scheduled jobs.

## Prerequisites and Configuration

* **Application Updates:** Ensure Discovery and Service Mapping Patterns, Visibility Content, and CMDB CI Class Models are up to date.
* **MID Server Setup:** Deploy and connect a dedicated MID Server with network access to Nutanix Prism Central and Prism Element. Install Nutanix SSL certificates into the MID Server's Java Runtime Environment (JRE) to enable secure API communication.
* **API Permissions:** Verify read-only access for required REST API endpoints for both v1-3 and v4 APIs, noting that some v1 endpoints remain necessary due to legacy support.
* **Prism Central Version:** Nutanix Prism Central must be at least version 7.3 to utilize the v4 API.
* **MID Server Properties:** Enable Nutanix v4 discovery by setting the MID Server property to the exact v4 version. Properties can also restrict v4 event discovery to specific Prism Central instances.
* **Authentication:** Configure basic authentication credentials for API access.
* **Discovery Scheduling:** Create a serverless discovery schedule targeting Nutanix components.
* **Integration with VMware:** To link Nutanix components hosted on ESX clusters to their VMware clusters, run VMware probe discovery prior to Nutanix discovery. Otherwise, Nutanix components link to Prism Central by default.
* **Optional Performance Optimization:** Disable tag discovery in the Nutanix Components pattern if numerous tags cause performance issues.
* **Batch Size Adjustment:** The deletion batch size for redundant Nutanix VM-to-host relationships can be tuned via a system property (default 1000).

## Data Collected During Discovery

The Nutanix Components pattern populates Nutanix-related Configuration Items (CIs) in the CMDB, including but not limited to:

* **Controller VMs:** Details such as name, UUID, memory, power state, hypervisor type, and description.
* **Clusters:** Attributes like cluster name, IP address, version, subnet details, time zone, hypervisor types, NTP servers, number of nodes, and serial numbers.
* **Hosts:** CPU core count, threads, speed, RAM, and serial numbers (serial numbers not applicable for v4 API).
* **Storage Pools and Containers:** Identification data, size (note size is not applicable for v4 pools), replication factors, deduplication, compression, and erasure codes.
* **Virtual Machine Instances:** CPU count, memory, state, and description.
* **Prism Central Instances:** Identified by IP or DNS name and object ID.

## CI Relationships

Discovery establishes relationships among Nutanix components to accurately model the environment:

* Clusters contain hosts and VMs; hosts register VMs; clusters manage storage pools and are managed by Prism Central.
* For AHV-hosted components, Controller VMs run on Nutanix VMs and define storage pools.
* For ESX-hosted components, Controller VMs run on VMware VMs and clusters when VMware discovery is run; otherwise, they link to Prism Central.

## Event Discovery

The Nutanix VM Event and Host Event patterns monitor state changes and trigger rediscovery. Event discovery requires:

* Nutainx Components discovery to have populated the Prism Central table.
* MID Servers with appropriate Nutanix capabilities.
* Discovery and Service Mapping Patterns version 1.31.0 or higher for v4 support.
* Enabling the scheduled jobs for event discovery.

## Tag Discovery

The pattern collects tags for Nutanix hosts and VMs, storing them in the Key Value table linked to configuration items. Tag discovery can be disabled if performance is impacted by numerous tags.

## Reporting and Dashboards

After discovery runs, the Nutanix dashboard becomes available under Self-Service \> Dashboards and provides reports based on CMDB data. Upgraded Discovery Admin Workspace versions offer enhanced insights.  
The ServiceNow
Discovery application uses the Nutanix Components pattern to find components of the Nutanix Acropolis solution containing Nutanix Prism Central version 2024.3.1.8 or Nutanix Prism Element 7.0.1.6. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
The Nutanix Components pattern uses REST APIs to collect information about the Acropolis deployment components.

Starting with version 1.29.0, Discovery and Service Mapping Patterns supports Nutanix v4 discovery. When you switch to v4, Discovery creates new pool and container records, while existing records stop being updated.

## Request apps on the Store {#nutanix-pattern__section_dbb_kgm_rlb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#nutanix-pattern__inline-send-to-store}

## Nutanix events {#nutanix-pattern__section_nutanix_events}

The Nutanix VM Event pattern finds events for virtual machines (VMs) in the Nutanix deployment and triggers rediscovery when a state change is detected. Starting with Discovery and Service Mapping Patterns version 1.31.0, the VM Event pattern also supports API v4, and the Nutanix Host Event pattern detects state changes for Nutanix hosts using API v4. Both patterns run every five minutes by default, but are inactive until you enable the relevant scheduled job.  
{#nutanix-pattern__table_nutanix_event_patterns__entry__3}

| Pattern | CI | API version |
|-|-|-|
| Nutanix VM Event | Nutanix Virtual Machine Instance \[cmdb_ci_nutanix_vm_instance\] | v1--3 and v4 |
| Nutanix Host Event | Nutanix Host \[cmdb_ci_nutanix_host\] | v4 only |
[Table 1. Patterns used for event discovery]

{#nutanix-pattern__table_nutanix_event_patterns}

## Prerequisites {#nutanix-pattern__section_xrh_4wz_ghb}

Verify that the following applications are up to date
:
    * Discovery and Service Mapping Patterns
    * Visibility Content
    * CMDB CI Class Models
    {#nutanix-pattern__ul_gqw_qfv_lfc}

Verify MID Server requirements
:   Deploy and connect a dedicated MID Server with network access to Prism Element and Prism Central.

Install Nutanix end-point SSL certificates for the MID Server JRE
:
    1. Collect the certificates by browsing the Nutanix Prism console on Internet Explorer.
    2. Add SSL certificates for the MID Server, as described in [Add SSL certificates for the MID Server](https://www.servicenow.com/docs/access?context=add-ssl-certificates&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US).
    3. Install Nutanix end-point SSL certificates for the MID Server JRE.
    {#nutanix-pattern__ol_c23_gs2_hvb}

Verify API permissions for v1-3
:   Verify that the user has read-only access to the following API requests:

    * /PrismGateway/services/rest/v1/vms
    * /PrismGateway/services/rest/v1/storage_pools
    * /PrismGateway/services/rest/v2.0/tasks/list
    * /PrismGateway/services/rest/v2.0/hosts
    * /PrismGateway/services/rest/v2.0/clusters
    * /PrismGateway/services/rest/v2.0/vms
    * /PrismGateway/services/rest/v2.0/storage_containers
    * /api/nutanix/v3/clusters/list
    * /api/nutanix/v3/categories/list
    * /api/nutanix/v3/categories/{category_keys}/list
    * /api/nutanix/v3/category/query
    {#nutanix-pattern__ul_ixd_ljv_2hb}

Verify API permissions for v4
:   Verify that the user has read-only access to the following GET APIs. Note that the API call referencing `/PrismGateway/services/rest/v1/vms` uses a legacy endpoint because it's not available yet in the
    newer API.

    * `/api/clustermgmt/v4/config/clusters`
    * `/api/clustermgmt/v4/config/clusters/{clusters_ID}/hosts​`
    * `/api/clustermgmt/v4/config/storage-containers`
    * `/api/vmm/v4/ahv/config/vms`
    * `/PrismGateway/services/rest/v1/vms`
    * `/api/prism/v4/config/categories?$expand=associations​`
    * `/api/prism/v4/config/categories/{categories_ID}?$limit=extId&$expand=detailedAssociations`
    {#nutanix-pattern__ul_x1j_b53_ygc}

Verify Prism Central version for v4 API
:   Ensure that Prism Central is at least version 7.3 to use the v4 API.

Set MID Server property to discover v4
:   Enable Nutanix v4 discovery by setting the MID Server property value to the exact v4 version. For more information, see [Enable Nutanix v4 discovery](https://www.servicenow.com/docs/QGPapdbHPI5N9ea725KTsQ "Enable Nutanix v4 discovery by setting the MID Server property value to the exact v4 version.").

Configure basic authentication credentials
:   For more information, see [Basic authentication credentials](https://www.servicenow.com/docs/access?context=r_BasicAuthCredentialsForm&version=zurich&pubname=zurich-platform-security&ft:locale=en-US).

Create a serverless discovery schedule
:   Create a discovery schedule to perform targeted discovery of Nutanix components. For more information, see [Create a serverless schedule for Nutanix Acropolis discovery](https://www.servicenow.com/docs/CkNVeK_Izgonl6VDh5l5YA "Create a serverless schedule to discover Nutanix Acropolis using REST API.").

Link Nutanix components to ESX clusters
:   The Nutanix Components pattern can discover Nutanix components hosted on ESX clusters, like storage pools, storage containers, and Controller Virtual Machine (CVM), but not ESX clusters themselves. Run VMware probe discovery before the Nutanix pattern discovery to link the Nutanix components to their ESX clusters. If you don't, the Nutanix components are linked to Nutanix Prism instead. For more information on VMware probe discovery, see [Discovery for VMware virtualization](https://www.servicenow.com/docs/9tCLAJ0nTpMSb~P1PXMvNg "A Discovery schedule for VMware virtualization discovers vCenter and ESX hosts and individual ESXi hosts that manage VMs and related components without a vCenter.").

(Optional) Disable CI tag discovery
:   The Nutanix Components pattern discovers tags for Nutanix hosts and virtual machines. If you have dozens of tags in your deployment, it might slow down the discovery causing performance issues. You can disable the CI tag discovery by performing the
    following steps:

    1. Navigate to Pattern DesignerDiscovery Patterns.
    2. Select the Nutanix Components pattern.
    3. Under Extension Section, select the check box for Categories (Tags) and select Remove.
    4. Select Save.
    {#nutanix-pattern__ol_obf_g41_h3b}

Adjust the batch size for removing redundant relationship data
:   The sn_itom_pattern.nutanix_relations_deletion_batch_size property sets the batch size for deleting relations between Nutanix Virtual Machine Instance and Nutanix Host. The default value is 1000; you can adjust this batch size as needed.

Configure Nutanix events
:
    * Verify that Nutanix Components discovery has run and that the Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\] table is populated.
    * Verify that the MID Servers for Nutanix event discovery have All or Nutanix capability.
    * For v4 event discovery, verify that at least version 1.31.0 of Discovery and Service Mapping Patterns is installed.
    * To restrict v4 event discovery to specific Prism Central instances, see [Restrict Nutanix v4 event discovery to specific Prism Centrals](https://www.servicenow.com/docs/ewZkJ5dLu4iD0hHWBaXW8w "Create a MID Server property to target specific Prism Central instances for Nutanix v4 event discovery.").
    * Enable the event discovery scheduled job. For more information, see [Enable Nutanix event discovery](https://www.servicenow.com/docs/rD9H8tTEzomZnX9Qi6LUnw "Activate the Nutanix events scheduled job to trigger rediscovery of Nutanix components when a state change is detected.").
    {#nutanix-pattern__ul_nutanix_events_prereqs}

## Data collected by Discovery during horizontal discovery {#nutanix-pattern__section_xj5_j3q_fdb}

Discovery populates the data in the CMDB when running the Nutanix Components pattern.  
Note:  
API v4 calls might retrieve or populate different values compared to v1-3. For more information, search the [Nutanix documentation](https://www.nutanix.dev/) for the "API Reference v4 Introduction" article.  
{#nutanix-pattern__table_n2r_c2d_k2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The name of the Nutanix Controller VM. |
| VM ID \[vm_id\] | The universally unique identifier (UUID) of the Nutanix Controller VM. |
| Object ID \[object_id\] | The ID of the Nutanix Controller VM. |
| Memory (MB) \[memory\] | The memory size of the Nutanix Controller VM in Megabytes (MB). |
| State \[state\] | The power state of the Nutanix Controller VM (on/off). |
| Hypervisor Type \[hypervisor_type\] | The type of the hypervisor used for the Nutanix Controller VM. |
| Description \[short_description\] | The description defined for the virtual machine in the Nutanix console: Prism Central or Prism Element. |
[Table 2. Nutanix Controller VM \[cmdb_ci_nutanix_controller_vm\]]

{#nutanix-pattern__table_n2r_c2d_k2c}  
{#nutanix-pattern__table_nkk_w2d_k2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The name of the Nutanix Cluster. |
| IP Address \[ip_address\] | The IP address of the Nutanix Cluster. |
| Cluster ID \[cluster_id\] | The ID of the Nutanix Cluster. |
| Object ID \[object_id\] | The object ID of the Nutanix Cluster. |
| Version \[version\] | The Nutanix Cluster version. |
| Full Version \[full_version\] | The full version of the Nutanix Cluster. |
| Internal Subnet \[internal_subnet\] | The subnet of the internal IP address of the Nutanix Cluster. |
| External Subnet \[external_subnet\] | The subnet of the external IP address of the Nutanix Cluster. |
| Timezone \[timezone\] | The time zone of the Nutanix Cluster. |
| Hypervisor Types \[hypervisor_types\] | The type of the hypervisor used for the Nutanix Cluster. |
| NTP Servers \[ntp_servers\] | The Network Time Protocol (NTP) servers that are related to the Nutanix Cluster. |
| Number of Nodes \[num_nodes\] | The number of nodes connected to the Nutanix Cluster. |
| NCC Version \[ncc_version\] | The Nutanix Cluster Check (NCC) version. |
| Block Serial Numbers \[block_serial_numbers\] | The serial numbers of blocks of data connected to the Nutanix Cluster. |
[Table 3. Nutanix Cluster \[cmdb_ci_nutanix_cluster\]]

{#nutanix-pattern__table_nkk_w2d_k2c}  
{#nutanix-pattern__table_u55_5fd_k2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The name of the Nutanix host. |
| Object ID \[object_id\] | The ID of the Nutanix host. |
| CPU core count \[cpu_core_count\] | The number of Nutanix host cores. |
| CPU core thread \[cpu_core_thread\] | The number of threads of the Nutanix host. |
| CPU speed (MHz) \[cpu_speed\] | The CPU speed of the Nutanix host in MHz. |
| CPU count \[cpu_count\] | The number of CPU sockets of the Nutanix host. |
| RAM (MB) \[ram\] | The memory of the host in Megabites (MB). |
| Serial number \[serial_number\] | Serial number of the Nutanix host. This field is not applicable for v4. |
[Table 4. Nutanix Host \[cmdb_ci_nutanix_host\]]

{#nutanix-pattern__table_u55_5fd_k2c}  
{#nutanix-pattern__table_j3c_hgd_k2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | * v1-3: The name of the Nutanix storage pool. * v4: Cluster name. {#nutanix-pattern__ul_zqf_453_ygc} |
| Pool ID \[pool_id\] | * v1-3: The UUID of the Nutanix storage pool. * v4: The external ID (extId) of the pool retrieved from the Nutanix Storage Container. {#nutanix-pattern__ul_ag5_r53_ygc} |
| Object ID \[object_id\] | * v1-3: The ID of the Nutanix storage pool. * v4: The external ID (extId) of the pool retrieved from the Nutanix Storage Container. {#nutanix-pattern__ul_qr5_t53_ygc} |
| Size \[size\] | The size of the Nutanix storage pool. This field is not applicable for v4. |
[Table 5. Nutanix Storage Pool \[cmdb_ci_nutanix_storage_pool\]]

{#nutanix-pattern__table_j3c_hgd_k2c}  
{#nutanix-pattern__table_l54_4gd_k2c__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The ID of the Nutanix container. |
| Container ID \[container_id\] | The UUID of the Nutanix container. |
| Name \[name\] | The name of the Nutanix container. |
| Replication Factor \[replication_factor\] | The number of copies created for the data stored on this Nutanix storage container. |
| Deduplication \[deduplication\] | The deduplication is enabled or disabled for the Nutanix container. |
| Compression \[compression\] | The compression is enabled or disabled for the Nutanix container. |
| Erasure Code \[erasure_code\] | The erasure of code is enabled or disabled for the Nutanix container. |
| Size \[size\] | The Nutanix container size calculated dynamically during discovery. |
[Table 6. Nutanix Storage Container \[cmdb_ci_nutanix_storage_container\]]

{#nutanix-pattern__table_l54_4gd_k2c}  
{#nutanix-pattern__table_uyc_phd_k2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The name of the Nutanix Controller VM. |
| VM Instance ID \[vm_inst_id\] | The universally unique identifier (UUID) of the Nutanix Controller VM. |
| Object ID \[object_id\] | The ID of the Nutanix Controller VM. |
| CPUs \[cpus\] | The number of CPUs that the VM has. |
| Memory (MB) \[memory\] | The memory size of the Nutanix Controller VM in Megabytes (MB). |
| State \[state\] | The power state of the Nutanix Controller VM (on/off). |
| Description \[short_description\] | The description defined for the virtual machine in the Nutanix console: Prism Central or Prism Element. |
[Table 7. Nutanix Virtual Machine Instance \[cmdb_ci_nutanix_vm_instance\]]

{#nutanix-pattern__table_uyc_phd_k2c}  
{#nutanix-pattern__table_fkq_bjd_k2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The name of the Nutanix Prism Central multi-cluster manager. * PrismCentral@\<IP_ADDRESS\>: When the IP address is associated with the Prism Central instance, in the following scenarios: * During quick discovery using HTTP classification. * During serverless discovery if IP address was entered in PRISM_Address parameter value. {#nutanix-pattern__ul_ywx_wjd_k2c} * PrismCentral@\<DNS_NAME\>: When the DNS name is associated with the Prism Central instance and was entered in PRISM_Address parameter value during serverless discovery. {#nutanix-pattern__ul_oq4_2jd_k2c} |
| Object ID \[object_id\] | The ID of the Nutanix Prism Central. This field has the same value as the Name field. * PrismCentral@\<IP_ADDRESS\>: When the IP address is associated with the Prism Central instance, in the following scenarios: * During quick discovery using HTTP classification. * During serverless discovery if IP address was entered in PRISM_Address parameter value. {#nutanix-pattern__ul_hrf_5q3_k2c} * PrismCentral@\<DNS_NAME\>: When the DNS name is associated with the Prism Central instance and was entered in PRISM_Address parameter value during serverless discovery. {#nutanix-pattern__ul_tyh_fjd_k2c} |
[Table 8. Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\]]

{#nutanix-pattern__table_fkq_bjd_k2c}  
The graphic illustrates CIs that are part of the Acropolis discovery in deployments that use Nutanix AHV for virtualization. Figure 1. Nutanix components   

The graphic illustrates CIs that are part of the Acropolis discovery in deployments that use VMware software for virtualization. Figure 2. Nutanix components in deployments using VMware software   

The graphic illustrates the Server and Nutanix VM Instance relationship.  

## CI relationships {#nutanix-pattern__section_4w5f_pq_fdb}

These relationships are created to support all Nutanix discovery, regardless of hypervisor.  
{#nutanix-pattern__table_tzw_qc2_nhc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Nutanix Cluster \[cmdb_ci_nutanix_cluster\] | Members::Member of | Nutanix Host \[cmdb_ci_nutanix_host\] |
| Nutanix Virtual Machine Instance \[cmdb_ci_nutanix_vm_instance\] | Registered::Has registered | Nutanix Host \[cmdb_ci_nutanix_host\] |
| Nutanix Virtual Machine Instance \[cmdb_ci_nutanix_vm_instance\] | Hosted on::Hosts | Nutanix Cluster \[cmdb_ci_nutanix_cluster\] |
| Nutanix Storage Pool \[cmdb_ci_nutanix_storage_pool\] | Contains::Contained by | Nutanix Storage Container \[cmdb_ci_nutanix_storage_container\] |
| Servers \[cmdb_ci_server\] | Instantiates::Instantiated by | Nutanix Virtual Machine Instance \[cmdb_ci_nutanix_vm_instance\] |
| Nutanix Cluster \[cmdb_ci_nutanix_cluster\] | Managed by::Manages | Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\] |
[ ]

{#nutanix-pattern__table_tzw_qc2_nhc}

These relationships are created to support Nutanix discovery for components hosted on AHV clusters.  
{#nutanix-pattern__table_ysf_fpq_f987b__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Nutanix Controller VM \[cmdb_ci_nutanix_controller_vm\] | Runs on::Runs | Nutanix Virtual Machine Instance \[cmdb_ci_nutanix_vm_instance\] |
| Nutanix Cluster \[cmdb_ci_nutanix_cluster\] | Defines resources for::Gets resources from | Nutanix Storage Pool \[cmdb_ci_nutanix_storage_pool\] |
[ ]

{#nutanix-pattern__table_ysf_fpq_f987b}

These relationships are created to support Nutanix discovery for components hosted on ESX clusters if you ran a VMware discovery.  
{#nutanix-pattern__table_acb_rqy_khc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Nutanix Controller VM \[cmdb_ci_nutanix_controller_vm\] | Runs on::Runs | VMware Virtual Machine Instance \[cmdb_ci_vmware_instance\] |
| VMware Cluster \[cmdb_ci_vmware_cluster\] | Defines resources for::Gets resources from | Nutanix Storage Pool \[cmdb_ci_nutanix_storage_pool\] |
[ ]

{#nutanix-pattern__table_acb_rqy_khc}

These relationships are created to support Nutanix discovery for components hosted on ESX clusters if you didn't run a VMware discovery.  
{#nutanix-pattern__table_rxj_5qy_khc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Nutanix Controller VM \[cmdb_ci_nutanix_controller_vm\] | Hosted on::Hosts | Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\] |
| Nutanix Storage Pool \[cmdb_ci_nutanix_storage_pool\] | Hosted on::Hosts | Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\] |
[ ]

{#nutanix-pattern__table_rxj_5qy_khc}

## Tag discovery {#nutanix-pattern__section_wqy_gvh_hgc}

The Nutanix Components pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table.  
{#nutanix-pattern__table_q5k_hjd_k2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | The category key. |
| Value \[value\] | The category value. |
| Configuration item \[configuration_item\] | References the Nutanix Host \[cmdb_ci_nutanix_host\] table. |
[Table 9. Key Value \[cmdb_key_value\]]

{#nutanix-pattern__table_q5k_hjd_k2c}

## Dashboard {#nutanix-pattern__section_hng_lcy_tjb}

The dashboard contains reports that query the Configuration Management Database (CMDB) and display the results. The information is displayed only after the pattern has discovered the infrastructure.

To display the dashboard, navigate to Self-ServiceDashboardsAllNutanix.

After upgrading to Discovery Admin Workspace version 1.3.1 (August 2024 Store), you can navigate to WorkspacesDiscovery Admin WorkspaceInsights and use the enhanced dashboard.
* **[Create a serverless schedule for Nutanix Acropolis discovery](https://www.servicenow.com/docs/CkNVeK_Izgonl6VDh5l5YA)**   
  Create a serverless schedule to discover Nutanix Acropolis using REST API.
* **[Enable Nutanix v4 discovery](https://www.servicenow.com/docs/QGPapdbHPI5N9ea725KTsQ)**   
  Enable Nutanix v4 discovery by setting the MID Server property value to the exact v4 version.
* **[Restrict Nutanix v4 event discovery to specific Prism Centrals](https://www.servicenow.com/docs/ewZkJ5dLu4iD0hHWBaXW8w)**   
  Create a MID Server property to target specific Prism Central instances for Nutanix v4 event discovery.
* **[Enable Nutanix event discovery](https://www.servicenow.com/docs/rD9H8tTEzomZnX9Qi6LUnw)**   
  Activate the Nutanix events scheduled job to trigger rediscovery of Nutanix components when a state change is detected.

*[\>]: and then