Version 107 of the "Nutanix: Base Pack" PowerPack includes new Dynamic Applications, device classes, and dashboards for monitoring Nutanix Enterprise AI devices; new "Healthy" event policies designed to clear existing "Minor" and "Critical" event policies; and new event policy descriptions for better Skylar AI utilization. It also includes updates to support Nutanix v4 REST APIs and Python 3.11 execution environments, and addresses several issues from previous releases.

• Minimum Required Skylar One (SL1) Version: 12.3.1

• Support Status: GA

Before You Install or Upgrade

Ensure that you are running version 12.3.1 or later of Skylar One before installing the "Nutanix: Base Pack" PowerPack.

For details on upgrading Skylar One, see the relevant Skylar One Platform Release Notes.

You can monitor Prism Elements or Prism Central. You must choose between monitoring Prism Elements or Prism Central as the root device, and then run discovery accordingly. It is recommended that you monitor Prism Central in all cases, unless you have only Prism Elements instances with no Prism Central instances.

Installation and Upgrade Process

By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.

To install this PowerPack:

1. Search for and download the PowerPack from the PowerPacks page at the ScienceLogic Support Center (Skylar One > PowerPacks).
2. In Skylar One (formerly SL1), go to the PowerPacks page (System > Manage > PowerPacks).
3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
4. Click Browse and navigate to the PowerPack file from step 1.
5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
6. Click Install. The PowerPack is added to the PowerPack Manager page.

For more information about using the PowerPack, see the Monitoring Nutanix manual.

Features

This release includes the following features:

• Dynamic Applications that discover and collect configuration and performance data for Nutanix devices
• Event Policies and corresponding alerts that are triggered when Nutanix devices meet certain status criteria
• Device Classes for each type of Nutanix device monitored
• A sample Credential for discovering Nutanix devices
• Dashboards that display information about Nutanix instances and component devices
• Run Book Actions and Automation policies to assign the proper device class to the Nutanix root device

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in this release:

• Updated the PowerPack to support Nutanix v4 REST APIs. As part of this effort, the silo-low-code-steps-nutanix library was updated to support pagination and alert- and event-related custom steps in v4.

Not all v1, v2, and v3 collection objects have a Nutanix v4 REST API equivalent. As a result, the current versions of the collection objects will remain in the PowerPack. For more information about the collection objects that are missing in v4 and will still use the old API versions, see the "Nutanix Collection Objects Missing in API v4" appendix in the Monitoring Nutanix manual.

• Storage pool data is no longer available in Nutanix v4 REST API. Due to this change, Storage Pool components are not discovered and Storage Container components are created under the "Storage Pool Group" virtual device.

• Updated the PowerPack to work with Python 3.11 execution environments.

• Added the following Dynamic Applications to collect data for Nutanix Enterprise AI:

  • Nutanix: Enterprise AI Endpoint Discovery

  • Nutanix: Enterprise AI Endpoint Configuration

  • Nutanix: Enterprise AI Endpoint Performance

  • Nutanix: Enterprise AI Kubernetes Cluster Configuration

  • Nutanix: Enterprise AI Kubernetes Node Configuration

  • Nutanix: Enterprise AI Model Inventory

• Added a new "Nutanix Enterprise AI | Example" SOAP/XML credential for discovering Nutanix Enterprise AI devices.

• Added the following new device classes to support data collection of Nutanix Enterprise AI devices:

  • Enterprise AI

  • NAI Endpoint

• Added a new "Enterprise AI" device category to support data collection of Nutanix Enterprise AI devices.

• Added a new "Nutanix: Enterprise AI Dynamic Application Template" device template to allow Skylar One to align the new Nutanix: Enterprise AI Dynamic Applications to devices.

• Added the new "Nutanix: Enterprise AI root device reclassification is needed" event policy to update the Nutanix AI root device class.

• Added the new "Nutanix: Enterprise AI Classify Root Device Class" run book automation policy and corresponding "Nutanix: Enterprise AI Classify Root Device Class" run book action policy.

• Added a new "Enterprise AI Endpoint Performance – AP2 Performance Metrics" dashboard to the PowerPack. This dashboard provides visibility into key performance metrics for Enterprise AI endpoints, including GPU Count, GPU Memory Usage, GPU Utilization, CPU Usage, Memory Usage, and LLM Metrics API Usage.

• Updated all event policy descriptions with new text and consistent formatting to facilitate better utilization by Skylar AI. No event policy behavior was impacted by this change.

  If you have previously modified the descriptions of any event policies included in the PowerPack, then upgrading the PowerPack might overwrite those customizations.

• Added the following event policies that have a severity of "Healthy" and are designed to clear existing event policies with severities of "Minor" or "Critical":

  • Nutanix Cluster Alert [Healthy]

  • Nutanix CVM Alert [Healthy]

  • Nutanix Disk Alert [Healthy]

  • Nutanix Host Alert [Healthy]

  • Nutanix Prism Central Alert [Healthy]

  • Nutanix Storage Container Alert [Healthy]

  • Nutanix Storage Pool Alert [Healthy]

  • Nutanix Workload VM Alert [Healthy]

• To ease high CPU utilization on Data Collectors monitoring large numbers of Nutanix disk components, Nutanix Disk Dynamic Applications were updated to support bulk snippets. (Case: 00557086)

• To align device modeling across both Nutanix discovery Dynamic Applications, the External IP Address collection object now uses Distinguished Name (%C) as its component identifier, while the Unique ID collection object now uses both Unique Identifier (%U) and UUID as component identifiers. These changes ensure consistent device identity fields, correct field population, and proper API endpoint selection during health collection. (Case: 00564888) 

• Added a new collection object globally unique identifier (GUID) for "Block" devices. As a result, new "Block Appliance" components are created, and existing "Block Appliance" components move to Vanished Devices.

• Added the following collection objects to the "Nutanix: Storage Container Capacity" and "Nutanix: Usage Stats" Dynamic Applications:

  • DAS Disk Capacity Used

  • SSD Disk Capacity Used

• Added the new "Disk Count" collection object to the "Nutanix: Host Config & Disk Discovery" Dynamic Application.

Known Issues

The following known issues affect version 107 of the "Nutanix: Base Pack" PowerPack:

• When upgrading from version 102 or earlier of the PowerPack, the following stats, which were removed from version 103, will display as "No Data Found":

• Nutanix: VM I/O Stats: CPU Usage
• Nutanix: VM I/O Stats: CPU Utilization

• When discovering a Prism Central that contains Prism Element devices that have been previously discovered and user-disabled, the Prism Element devices will need to be re-enabled after the Prism Element devices have been moved to the new Prism Central device tree so that normal Dynamic Application alignment and data collection can proceed.

• When discovering Prism Element and Prism Central devices, do not include both types of devices in the IP list for discovery, as the DCM tree will not fully build out and will be missing component devices. It is recommended that you either discover individual Prism Element clusters, or discover a Prism Central device with multiple Prism Element clusters.