Applications Systems
Custom alert thresholds reset to global defaults for Nutanix VMs after database maintenance
Custom alert thresholds configured for individual Nutanix virtual machines, AHV hosts, or datastores can be removed after daily database maintenance, causing the affected objects to fall back to global default thresholds.
First published date
Last published date
Overview
This issue can occur when SolarWinds recreates certain Nutanix virtualization objects during database maintenance. When that happens, the internal object IDs change even though identifiers such as UUID or ManagedObjectID remain the same, and existing custom thresholds can be removed during cleanup.
Product section
Cause
During daily database maintenance, some Nutanix VM and datastore objects can be internally recreated, which changes their internal IDs. Cleanup logic can then treat the existing per-object thresholds as orphaned and remove them, even though the object still represents the same VM or datastore.
Resolution
As of July 9, 2026, the fix implementation date has not yet been defined. Please monitor this KB article or the product Release Notes for upcoming product fixes and enhancements.
Notes:
- A closely related datastore-specific variant of this behavior was addressed in a prior release; however, the Nutanix VM/AHV-host scenario described in this article is tracked separately and is not yet resolved.
- There is currently no reliable, supported workaround that preserves per-object custom thresholds for Nutanix VMs/AHV hosts across the daily Database Maintenance job. Re-applying the overrides will persist only until the next maintenance run.