Nutanix Objects Manual: Monitoring, Alerts, and Event Notifications

MONITORING AND ALERTS IN NUTANIX

OBJECTS

Monitor object store usage, bucket performance, and system alerts in Nutanix Objects, with visibility rules based on user roles in Prism Central.You can monitor the usage and the performance of object stores and buckets, and you can also view system-generated alerts for Nutanix Objects.Non-admin users can view the usage and performance of object stores and buckets, and also view system-generated alerts for objects only if assigned a role with View Object Store permission by the admin user in Prism Central. Admins are Super Admins or Prism Admins in Prism Central; non-admins are Prism Central users without admin privileges.For more information on the built-in roles in Prism Central, see Built-in Role Management in the Security Guide.For the object counts that are shown at the object store instance level, Nutanix Objects counts each upload of a multipart upload as a separate object until the object is finalized. At the bucket level, only finalized objects are counted.For example, if you upload 10 objects with 5 parts each, the object store instance shows a count of 50, while the bucket shows 0 until the uploads are complete.

Viewing Performance of Object Stores

You can view and analyze the performance of an object store by placing the cursor anywhere on the horizontal axis to display the value at that time. You can also select the time interval (last 1 hour, 3 hours, 6 hours, 12 hours, and 24 hours) from the pull-down list above the graphs.

About this taskTo view the performance of an object store, follow these steps:

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects.3. In the object stores table, click the name of the object store to view its performance.

| The | Object Store page appears. Objects | Monitoring and Alerts in Nutanix Objects | | | — | — |

4. Click Performance.

Figure 37: Object Store Performance Graph

The graph shows the following information:

bucket.

MB in each second.You can see the total in, total out, gets, puts, NFS reads, and NFS writes in a bucket.

the object in milliseconds.

Viewing Performance of Buckets

You can view and analyze the performance of a bucket by placing the cursor anywhere on the horizontal axis to display the value at that time. You can also select the time interval (last 1 hour, 3 hours, 6 hours, 12 hours, and 24 hours) from the pull-down list above the graphs.

About this task

Note: The Throughput chart shows data for each connection. This data is not the cumulative throughput

across all the clients and connections. To view the performance of a bucket, follow these steps:

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects. . In the object stores table, click the name of the object store to view its performance.

4. Click the Bucket tab, and then click the name of the bucket from the Buckets list table, and then click

Performance.

Figure 38: Bucket Performance Graph

The graph displays the performance of the bucket.

bucket.

second.You can see the total in, total out, gets, puts, NFS reads, and NFS writes in a bucket.

the object in milliseconds.

Viewing Object Store Usage

The Usage tab displays the physical and logical storage usage. You can view the space used across all buckets in an object store.

About this taskTo view the object store usage, follow these steps:

Procedure

1. Log on to the Prism Central web console. . In the Application Switcher, click Objects.3. In the object stores table, click the name of the object store to view its usage.

4. Click Usage > Usage Summary.

Figure 39: Object Store Usage

The storage usage section displays the following information:Physical Usage: Displays the physical capacity used by the object store on the cluster.

• Total used and total usable storage for the cluster.• Space used across all buckets on the existing cluster displayed in a bar.• Total and free physical capacity of the cluster.• Logical capacity assigned for the object store.Logical Usage: Displays the logical capacity used by the object store on the cluster. As the

Redundancy Factor is 2 (RF-2), the data is stored in two backups.

• Data stored locally• Data tiered to another S3 endpoint

Assigning Quota Policy to a User

Assigning a quota policy to a user Nutanix Objects to set soft and hard thresholds on storage limits of all buckets owned by the user and number of buckets created by the user within an object store. You can assign quota policy to multiple users at the same time. If a soft threshold is set and if any user exceeds the limit, they can still create buckets and objects, however an alert is raised in the Alerts page. However, if a hard threshold is set, then the user is restricted from exceeding the limit. For example, if a user has 20 TB storage and has six buckets, then storage for all the six buckets will be accounted. If you are an owner of a bucket and have shared your bucket with multiple users, then your storage quota will be used up even if other users use the shared bucket storage. Quota policies will be automatically removed within 24 hours after the user is deleted. If some multi-part operations are pending, those pending parts will count towards the quota. Objects | Monitoring and Alerts in Nutanix Objects |

Before you beginA non-admin user can assign quota policy to a user only after the administrator creates an access control policy on a role in Prism Central for the non-admin user. The specific role must have the following minimum permissions:

• Create Quota Policy• Delete Quota Policy• View Quota Policy• View Object Store

Note: Administrators and non-admin users are Prism Central users with the following roles:

• Administrator - A Super Admin or a Prism Admin in Prism Central.• Non-admin user - A Prism Central user without any administrator privileges.For more information on the built-in roles in Prism Central, see

Built-in Role Management in the Security Guide.

About this task

• You cannot list the buckets only owned by a particular user. So, if you have exceeded your storage

quota and try to delete a bucket shared with you to release the storage space, the quota level remains as is. You have to delete your own bucket to release the storage space.For example, if user A has exceeded the storage quota and tries to list all the buckets, the bucket list will also contain the buckets that were shared with user A by user B. To release the storage space within user A quotas, if user A deletes objects in the buckets shared with user A by user B, the quota level remains as is.You can run get-bucket-acl command on the bucket to list the user owned buckets, and then delete the data from that bucket.

• Quota policies are enforced for buckets or space usage across all namespaces, federated or non-

federated alike.

• If federation is enabled, quotas for a particular owner/user are enforced only on the OSS cluster where

the policy was created and not on other OSS clusters which are part of the same federation.

Important:

• Usage is accounted under the owner of the bucket, and not under the user who uploaded the

objects to the bucket.For example, user A and user B each have a 50 GiB quota. User A creates bucket X and shares it with user B, and both users upload 10 GiB to bucket X. User A’s usage is 20 GiB and user B’s usage is 0 GiB, because all usage is attributed to user A, the owner of bucket X.

• Admin-created buckets (buckets created from the UI) are not accounted for under any quota.

To assign a quota policy to a user, follow these steps:

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects. Objects | Monitoring and Alerts in Nutanix Objects |

3. In the object stores table, click the name of the object store to see the object store usage and to assign

quota policy to the users.

4. Click Usage > Quota Policy.5. Select the user for which you want to create the quota policy. If you are creating quota policy for the first time, skip this step. 6. Click + Create Policy.

Figure 40: Configure Quota

7. Select a user or multiple users from the People drop-down. You can create quote policy for multiple users simultaneously, but you cannot assign multiple quotas to the same user. 8. In the Quota Limit section, select either one check box or both check boxes, and enter the limit.

Capacity Limit cannot be larger than the current available storage.

create. . In the Quota Limit Enforcement section, select any of the following, and then click Save.

request is not blocked. You can always update the existing policy.A list of users with the configured storage- and bucket-quota, and the current usage is displayed.When the storage usage or bucket usage reaches 90% of the defined limit, you are notified with an exclamation mark.A background task checks for any violation of quota policies and generates this alert. So, it can take about an hour to generate the alert. On a heavily loaded object store, it can take up to a day to generate an alert. What to do nextYou can view the alerts. For more information, see Viewing Nutanix Objects Alerts on page 172.

Viewing Nutanix Objects Alerts

You can view any informational, warning, and critical alerts in a tabular format. The table presents each alert with the color-coded severity level, a description of the alert, and the time stamp.

About this task

Note: Nutanix Objects-related alerts are now displayed in the Prism Central Alerts section as well. You see

a banner at the top of the page to open the Prism Central alerts page. To view object store alerts, follow these steps:

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects.3. In the object stores table, click the name of the object store.

| The | Object Store page appears. Objects | Monitoring and Alerts in Nutanix Objects | | | — | — |

4. Click the Alerts tab.

Figure 41: Alerts List in the Nutanix Objects Alerts Page

The alerts table displays the following information:

Table 15: Alerts Table

Note:

• Silencing alerts cannot be done from Prism Central alerts page.• Silencing of alerts is temporary.

Objects alerts will be the object store name.

Figure 42: Alerts List in the Prism Central Alerts page

Nutanix Objects Specific Alerts

The following tables describe the Nutanix Objects specific alerts.Apart from the Nutanix Objects specific alerts, alerts that monitor the underlying infrastructure of the Nutanix Objects clusters are also triggered. For more information on these alerts, contact Nutanix Support at https://portal.nutanix.com. For more information on MSP alerts on Nutanix Objects, see MSP Alerts on Nutanix Objects Clusters on page 183.

Table 16: Nutanix Objects Alert - High Time to First Byte

Table 17: Nutanix Objects Alert - High Object Store Usage

Table 18: Nutanix Objects Alert - High Error Rate

Table 19: Nutanix Objects Alert - Endpoint Unreachable

Table 20: Nutanix Objects Replication Alert - Replication Pause Time For a Bucket Exceeded by 24

Hours

Table 21: Nutanix Objects Replication Alert - Last replication sync time for a bucket exceeded by 12

hours

Table 22: Nutanix Objects Replication Alert - Last replication sync time for a bucket exceeded by 3

days

Table 23: Nutanix Objects Replication Alert - Replication Endpoint Storage Full

Table 24: Nutanix Objects Replication Alert - Replication Endpoint Unreachable

Table 25: Nutanix Objects Replication Alert - Bucket Sync Completed

Table 26: Nutanix Objects Replication Alert - Few Nonconforming Nutanix Objects Skipped during

Sync

Table 27: Nutanix Objects Replication Alert - Replication Sync Operation on Bucket Stalled

Name kBucketSyncProgressStalled

Table 28: Nutanix Objects Replication Alert - Bucket Replication Sync has Pending Replication

Entries

Table 29: Nutanix Objects NFS Alert - High NFS Ops Drop Rate

Table 30: Nutanix Objects Too Many Delete Markers

Table 31: Nutanix Objects Too Many Versions

MSP Alerts on Nutanix Objects Clusters

The following tables describe the MSP alerts on Nutanix Objects clusters. For more information on these alerts, contact Nutanix Support at https://portal.nutanix.com.

Table 32: MSP Alert - Kube Pod Crash Looping

Table 33: MSP Alert - Kube Persistent Volume Filling Up

Table 34: MSP Alert - Kube Client Certificate Expiration

Table 35: MSP Alert - Kube API Down

Table 36: MSP Alert - Kubelet Down

For more information on Nutanix Objects specific alerts, see Nutanix Objects Specific Alerts on page 174. Objects | Monitoring and Alerts in Nutanix Objects |

NUTANIX OBJECTS NOTIFICATIONS

Notifications for Nutanix Objects enables you to send the completed events logs to the configured endpoints in your Nutanix Objects instance. This helps you with centralized events log management, thus enabling you to monitor and analyze the logs and identify performance or configuration issues. TCP is the supported protocol for Nutanix Objects notifications.The following endpoints are supported for logging the notification events:

Enter the hostname or host IP address and port number of your Syslog server when configuring the endpoints. The Syslog server should be up and running when performing the endpoint configuration in your Nutanix Objects instance.

that provides persistent logs. Enter the hostname or host IP address and port number of your NATS streaming server when configuring the endpoints. NATS streaming server should be up and running when performing the endpoint configuration in your Nutanix Objects instance.

Note: The default topic used to create the NATS queue is OSSEvents. You can use this as the subject

while using the NATS client to connect to the NATS streaming server.

through a high-performance TCP network protocol. It can be deployed on bare-metal hardware, virtual machines, and containers in on-premise as well as cloud environments. Enter the hostname or host IP address and port number of your Kafka server when configuring the endpoints. The Kafka server should be up and running when performing the endpoint configuration in your Nutanix Objects instance.

Notification Types for Nutanix Objects

There are two types of notifications for Nutanix Objects that can be enabled for either successful, or failed, or both successful and failed instance-level and data events.

a bucket, delete a bucket, enable versioning, and so on. The following instance-level events are supported for successful, or failed, or both successful and failed events: Note: All the instance-level events notifications are enabled by default once you configure the endpoints. You cannot enable or disable the notifications for a single instance-level event.

Table 37: S3 APIs for Only Successful Instance-level Events

Table 38: S3 APIs for Only Failed Instance-level Events

Table 39: S3 APIs for Both Successful and Failed Instance-level Events

For more information, see

• Configuring Event Notifications in Nutanix Objects for Syslog on page 191.• Configuring Event Notifications in Nutanix Objects for Kafka on page 197

Objects | Nutanix Objects Notifications |

• Configuring Event Notifications in Nutanix Objects for NATS on page 194The following is the structure of the notification output for instance-level events that get published to the

endpoints. {“EventType”:“s3:BucketCreated:Put”,“Key”:“first”,“Records”: [{“eventError”:“”,“eventVersion”:“2.0”,“eventSource”:“aws:s3”,“awsRegion”:“us- east-1”,“eventTime”:“2022-02-09T07:40:13Z”,“eventName”:“s3:BucketCreated:Put”,“userIdentity”: {“principalId”:“[email protected]”},“requestParameters”: {“sourceIPAddress”:“10.44.91.64”},“responseElements”: {“x-amz-id-2”:“110000+1229+2129+240”,“x-amz-request- id”:“110000+1229+2129+240”,“x-ntnx-origin-endpoint”:“0.0.0.0”},“s3”: {“s3SchemaVersion”:“1.0”,“configurationId”:“SuccessfulWriteManagementEvent”,“OSSDomain”:“rc4.eng.nutanix.com”,“bucket”: {“name”:“frst”,“ownerIdentity”: {“principalId”:“[email protected]”},“arn”:“arn:aws:s3:::frst”}}}],“level”:“info”,“msg”:“”,“time”:“2022-02-09T07:40:13Z”}

bucket. To enable notifications for successful, or failed, or both data events for a bucket, you need to

Subset of objects. For more information, see Creating Notification Rules for Data Events in Nutanix

Objects on page 201.The following is the structure of the notification output for data events that get published to the endpoints. {“EventType”:“s3:ObjectCreated:Put”,“Key”:“put”,“Records”: [{“eventError”:“”,“eventVersion”:“2.0”,“eventSource”:“aws:s3”,“awsRegion”:“us- east-1”,“eventTime”:“2022-02-09T08:04:48Z”,“eventName”:“s3:ObjectCreated:Put”,“userIdentity”: {“principalId”:“[email protected]”},“requestParameters”: {“sourceIPAddress”:“10.44.91.64”},“responseElements”: {“x-amz-id-2”:“110000+1229+2791+297”,“x-amz-request- id”:“110000+1229+2791+297”,“x-ntnx-origin-endpoint”:“0.0.0.0”},“s3”: {“s3SchemaVersion”:“1.0”,“configurationId”:“5836c513-51ef-45a9-9c84-6a0c01996e40”,“OSSDomain”:“rc4.eng.nutanix.com”,“bucket”: {“name”:“put”,“ownerIdentity”: {“principalId”:“[email protected]”},“arn”:“arn:aws:s3:::put”},“object”: {“key”:“csv.docx”,“size”:“31”,“eTag”:“c7a74379a77360a6b85926adb8b2aafb”,“versionId”:“1”,“sequencer”:“110000+1229+2791+297”}}}],“level”:“info”,“msg”:“”,“time”:“2022-02-09T08:04:48Z”} The following data events are supported for successful, or failed, or both successful and failed events:

Note: You can enable notifications for all Nutanix Objects Create Events, Nutanix Objects Access Events,

or Nutanix Objects Delete Events, or you can choose to enable notifications for one or more sub-categories of Nutanix Objects Create Events (such as Put, Post, Copy, Multipart Upload Complete), Nutanix Objects Access Events (such as Get, Head), or Nutanix Objects Delete Events (such as Delete, Delete Markers).

Table 40: S3 APIs for Only Successful Data Events

Table 41: S3 APIs for Only Failed Data Events

Table 42: S3 APIs for Both Successful and Failed Data Events

Configuring Event Notifications in Nutanix Objects for Syslog

Specify endpoints when configuring event notifications. By default, only successful events are logged. You can choose success, failure, both, or none. Before you beginYou must set up and maintain your own Syslog, NATS, or Kafka servers.

About this taskNutanix Objects supports event notifications through Syslog, NATS, or Kafka. To log operations, enable

notifications to one of these services. Nutanix does not manage these services.Non-admin users can configure event notifications only if an admin assigns them a role with specific

Endpoint, and View Object store. Admins are Super Admins or Prism Admins in Prism Central;

non-admins are Prism Central users without admin privileges. For more information, see Built-in Role Management in the Nutanix Security Guide.To configure Syslog notifications, follow these steps:

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects.3. In the object stores table, click the name of the object store to view its performance.

4. Click Endpoints > Notification Endpoints.

these endpoints or all of them.When you add a notification endpoint (Syslog, NATS, or Kafka) with correctly formatted fields, the operation succeeds even if the endpoint is unreachable or invalid. Errors during setup appear on the Object Store list page.

5. Click Actions > Enable

Endpoint is enabled. Objects | Nutanix Objects Notifications |

6. For a syslog endpoint, click Actions > Edit

Edit notification endpoint window appears. . In Syslog tab, specify the server connection details.

Important: Syslog server must be up and running when performing the endpoint configuration in your

Nutanix Objects instance.

Figure 43: Notification Endpoints: Syslog

Objects | Nutanix Objects Notifications |

name:Port format.

endpoints. 8. Click Save to complete the events notification configuration.

Note: After saving notification endpoints for an object store, the notification status might take one minute

to display correctly. Also, changes to the notification configuration can take up to five minutes to take effect. What to do nextTo configure Kafka and NATS notification, see Configuring Event Notifications in Nutanix Objects for Kafka on page 197, Configuring Event Notifications in Nutanix Objects for NATS on page 194.You can now create notification rules for data events of the bucket, see Creating Notification Rules for Data Events in Nutanix Objects on page 201.

Configuring Event Notifications in Nutanix Objects for NATS

Specify endpoints when configuring event notifications. By default, only successful events are logged. You can choose success, failure, both, or none. Before you beginYou must set up and maintain your own Syslog, NATS, or Kafka servers.

About this taskNutanix Objects supports event notifications through Syslog, NATS, or Kafka. To log operations, enable

notifications to one of these services. Nutanix does not manage these services.Non-admin users can configure event notifications only if an admin assigns them a role with specific

Endpoint, and View Object store. Admins are Super Admins or Prism Admins in Prism Central;

non-admins are Prism Central users without admin privileges. For more information, see Built-in Role Management in the Nutanix Security Guide.To configure events notifications, follow these steps:

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects. . In the object stores table, click the name of the object store to view its performance.

4. Click Endpoints > Notification Endpoints.

these endpoints or all of them.When you add a notification endpoint (Syslog, NATS, or Kafka) with correctly formatted fields, the operation succeeds even if the endpoint is unreachable or invalid. Errors during setup appear on the Object Store list page.

5. Click Actions > Enable

Endpoint is enabled.

6. For a Nats-streaming endpoint, click Actions > Edit

Edit notification endpoint window appears. . In the Nats-streaming tab, specify the server connection details.

Important: Nats-streaming server must be up and running when performing the endpoint configuration

in your Nutanix Objects instance.

Figure 44: Notification Endpoints: Nats-Streaming

Objects | Nutanix Objects Notifications |

name:Port format.

8. Click Save to complete the events notification configuration.

Note: After saving notification endpoints for an object store, the notification status might take one minute

to display correctly. Also, changes to the notification configuration can take up to five minutes to take effect. What to do nextTo configure Kafka and syslog notification, see Configuring Event Notifications in Nutanix Objects for Kafka on page 197, Configuring Event Notifications in Nutanix Objects for Syslog on page 191.You can now create notification rules for data events of the bucket, see Creating Notification Rules for Data Events in Nutanix Objects on page 201.

Configuring Event Notifications in Nutanix Objects for Kafka

Specify endpoints when configuring event notifications. By default, only successful events are logged. You can choose success, failure, both, or none. Before you beginYou must set up and maintain your own Syslog, NATS, or Kafka servers.

About this taskNutanix Objects supports event notifications through Syslog, NATS, or Kafka. To log operations, enable

notifications to one of these services. Nutanix does not manage these services.Non-admin users can configure event notifications only if an admin assigns them a role with specific

Endpoint, and View Object store. Admins are Super Admins or Prism Admins in Prism Central;

non-admins are Prism Central users without admin privileges. For more information, see Built-in Role Management in the Nutanix Security Guide.To configure events notifications, follow these steps:

Procedure

1. Log on to the Prism Central web console. . In the Application Switcher, click Objects.3. In the object stores table, click the name of the object store to view its performance.

4. Click Endpoints > Notification Endpoints.

these endpoints or all of them.When you add a notification endpoint (Syslog, NATS, or Kafka) with correctly formatted fields, the operation succeeds even if the endpoint is unreachable or invalid. Errors during setup appear on the Object Store list page.

5. Click Actions > Enable

Endpoint is enabled.

6. For a Kafka endpoint, click Actions > Edit

Edit notification endpoint window appears. . In the Kafka tab, specify the server connection and security protocol details. When adding a Kafka endpoint, if the OSSEvents topic does not exist, the system creates it. If it already exists, ensure it matches your Kafka server configuration.

Important: Kafka server must be up and running when performing the endpoint configuration in your

Nutanix Objects instance. Objects | Nutanix Objects Notifications |

Figure 45: Notification Endpoints: Kafka

In the Kafka tab, enter the following details: Objects | Nutanix Objects Notifications |

1. Server Address: Enter the host name and port number of your Kafka server in the hostname:port

format.

2. Security Protocol Configuration: Select one of the following options:

• Root certificate• Client certificate• Client key

following files:

• Root certificate• Client certificate• Client key

3. Topic: Enter the topic name. If the OSSEvents topic does not exist, the system creates it

automatically.

4. Publish Message Key: Select No key for no message key. Select /

for publishing as a key for management level events and / as a key for data level events.

5. Object Store Events: Select one of the following options to determine which events are logged:

8. Click Save to complete the events notification configuration.

Note: After saving notification endpoints for an object store, the notification status might take one minute

to display correctly. Also, changes to the notification configuration can take up to five minutes to take effect.

What to do nextTo configure Syslog and NATS notification, see Configuring Event Notifications in Nutanix Objects for

Syslog on page 191, Configuring Event Notifications in Nutanix Objects for NATS on page 194.You can now create notification rules for data events of the bucket, see Creating Notification Rules for Data Events in Nutanix Objects on page 201.

Creating Notification Rules for Data Events in Nutanix Objects

To track successfully completed data events, create notification rules for the buckets in Nutanix Objects.

About this taskNon-admin users can create notification rules for data events only if assigned a role with the following

permissions by the admin user in Prism Central. Objects | Nutanix Objects Notifications |

• View Notification Endpoint• Edit Buckets

Users with this permission can create notification rules for data events across all buckets in the assigned object stores.

• View Buckets• View Object StoreAdmins are Super Admins or Prism Admins in Prism Central; non-admins are Prism Central users without

admin privileges. For more information on the built-in roles in Prism Central, see Built-in Role Management in the Security Guide.To create a notification rule for a bucket, follow these steps.

Procedure

1. Log on to the Prism Central web console.2. In the Application Switcher, click Objects.3. In the object stores table, click the name of the object store to view its performance.

4. Click the Buckets tab, and then from the list of buckets, select the bucket for which you plan to create a

notification rule. 5. Click Data Event Notification.

6. Click Create Rule to open the Create Rule page. Configuring an endpoint is required to create notification rules. Configure endpoints that can be used to log both bucket events and data events. For more information, see Configuring Event Notifications in Nutanix Objects for Syslog on page 191, Configuring Event Notifications in Nutanix Objects for Kafka on page 197, and Configuring Event Notifications in Nutanix Objects for NATS on page 194. . (Optional) If a rule is already created for the bucket, click + Add Rule.

Figure 46: Create Rule

8. In the Create Rule page, follow these steps:

The endpoints configured on the object store are listed in the dropdown here.To configure endpoints for your Nutanix Objects instance, see Configuring Event Notifications in Nutanix Objects for Syslog on page 191, Configuring Event Notifications in Nutanix Objects Objects | Nutanix Objects Notifications |

for Kafka on page 197, and Configuring Event Notifications in Nutanix Objects for NATS on page 194.

Objects by entering a prefix, suffix, or both. Nutanix Objects with the prefix and suffix you specified are filtered and the rule applies to those objects.

Note:

objects.

• You can enter only one prefix and suffix. You can create another rule with a different

suffix and prefix.

Events, and Objects Delete Events, and choose from the following that you plan to log to the

endpoint.

Events, and Objects Delete Events are selected. 9. Click Save to complete, and then click Done to close the Create Rule page.

Event Notification page. You can click All Events or Number Events in the Events column to view

Objects | Nutanix Objects Notifications |

configured.

Figure 47: Configured Notification Events

Enabled. Objects | Nutanix Objects Notifications |

Last updated Oct 08, 2026