After a complex operation like a Hardware Non-Disruptive Upgrade (HWNDU), the Purity health services may occasionally stall or report generic errors like "health not responding." Standard alert commands (purealert list) might be empty or show generic "service unavailable" messages because the alerting service itself depends on the health system.
To troubleshoot this, the Implementation Engineer should dig deeper into the system's internal message log using puremessage list --open --hidden.
puremessage accesses the raw message bus of the array, which captures lower-level events than standard alerts.
--hidden is the critical flag here; it reveals internal system messages that are typically suppressed from the standard user view to avoid noise.
These hidden messages often contain the specific error codes or service failure reasons (e.g., "timeout waiting for daemon X") that explain why the health status is hanging. Providing this output to Pure Support significantly accelerates the root cause analysis. purearray diagnose is not a standard command for this purpose, and purealert watcher is for configuring notification recipients, not viewing log contents.