---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Restrict v4 event discovery by Prism Central

# Restrict Nutanix v4 event discovery to specific Prism Centrals {#ariaid-title1}

* Release version: Yokohama
* 
* Updated May 18, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create a MID Server property to target specific Prism Central instances for Nutanix v4 event discovery.

## Before you begin

* Verify that you have at least version 1.31.0 of Discovery and Service Mapping Patterns.
* 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.

{#restrict-nutanix-event-v4-property__ul_yfb_pj3_hjc}

Role required: discovery_admin.

## About this task

By default, Nutanix v4 event discovery runs against all Prism Central instances in the Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\] table, using any MID Server with the All or Nutanix capability. Starting with Discovery and Service Mapping Patterns version 1.31.0, you can create a MID Server property to target specific Prism Central instances. You can create multiple properties for different Prism Central and MID Server combinations.{#restrict-nutanix-event-v4-property__nutanix-events-v4-property-context-1}

## Procedure

1. Navigate to AllMID ServerProperties.
2. Select New.
3. Fill in the form.  
   {#restrict-nutanix-event-v4-property__table_nutanix_events_v4_property_form__entry__2}

   | Field | Description |
   |-|-|
   | Name | Property name. Enter <kbd class="ph userinput">sn_itom_pattern.nutanix_events_v4.prism_ips</kbd>. |
   | Value | Comma-separated list of IP addresses or hostnames of the Prism Central instances to target. The instances must already be present in the Nutanix Prism Central \[cmdb_ci_nutanix_prism_central\] table. |
   | MID server | MID Server to use for these Prism Central instances. Leave empty to use any MID Server with the All or Nutanix capability. |
   [Table 1. MID Server Property form]

   {#restrict-nutanix-event-v4-property__table_nutanix_events_v4_property_form}
4. Select Submit.
{#restrict-nutanix-event-v4-property__steps_ll5_tq3_hjc}

## What to do next

Enable the Nutanix event discovery scheduled job. For more information, see [Enable Nutanix event discovery](https://servicenow-prod.fluidtopics.net/GIHCdjlVOcAB2AGgCCPZwg "Activate the Nutanix events scheduled job to trigger rediscovery of Nutanix components when a state change is detected.").
**Related tasks**   

* [Enable Nutanix event discovery](https://servicenow-prod.fluidtopics.net/GIHCdjlVOcAB2AGgCCPZwg "Activate the Nutanix events scheduled job to trigger rediscovery of Nutanix components when a state change is detected.")  
**Related reference**   

* [Nutanix Acropolis discovery](https://servicenow-prod.fluidtopics.net/h2NN9W5DIkBtmg5HYYHlLw "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 may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")

*[\>]: and then