Disk utilization (% busy) is missing and shows as n/a in Databases Dashboard (4230123)

Disk metrics such as Disk Utilization work in the Infrastructure and Host dashboards, but the same disk information cannot be seen in the disk utilization column of the DB dashboard.

An error such as the following may appear in the database agent long

YYYY-MM-DD HH:MM:SS.SSS ECHO ERROR [testserver.example.com-ALPHA-wmiThreadPool-1-[DBSS_SQL_Server_Host][YYYY-MM-DD HH:MM:SS.SSS]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSPhysicalDiskProcessor processor of DBSS_SQL_Server_Host collection.
java.lang.RuntimeException: Failed to execute collection [DBSS_SQL_Server_Host], reason=failed to run WMI query: DBSS_Physical_Disk_Raw1_0_0_0.wmi

Operating system metrics such as CPU and memory may appear in the database dashboard without the Infrastructure cartridge (IC) having been successfully installed, agents created, and credentials having been configured.

• The DB agents do collect some OS information where the IC agent collects the remaining.
• The SQL Server agent will obtain the Disk Utilization Percentage (Disk Busy %) metrics from an Infrastructure agent when an associated resource mapping has been configured in the lockbox
• Both Oracle and DB2 database agents obtain all of the OS metrics (CPU, Memory and Disk) 
• The following are articles which describe functionality and diagnosis steps.

1. Verify that both the Infrastructure and HostAgents cartridges are enabled in Cartridge Inventory
2. Confirm that the HostAgents.gar has been deployed to the Agent Manager for the database agent.
3. Verify that Infrastructure agents (e.g. WindowsAgent, UnixAgent) are present and activated in Agent Status, with one for each monitored host.
4. Check the infrastructure dashboard to confirm that the disk monitoring is successfully occuring for the IC cartridge on the monitored host.
5. Confirm that two resource mappings are present in the credentials dashboard for each agent being monitored:
   1. For windows hosts
      1. "WMI Connection for DB Monitoring"
      2. "OS Monitoring by WMI"
   2. For Unix/Linux hosts
      1. "SSH Connection for DB Monitoring"
      2. "OS Monitoring by SSH"
6. Please see KB 104508 for more information on adding credentials for OS monitoring from database agents.

How do DB, VMWare, and IC cartridges work when collecting OS metrics?
Review the article to understand how these agents function.

Controlling System Access with Credentials 
The Credentials dashboard provides quick access to credentials and lockboxes. This dashboard provides at-a-glance information about the current state of credentials, lockboxes, credential clients, the alarms they generate and cartridge-specific credential views. Use it as a starting point for your credential management needs. To access this dashboard on the navigation panel, click "Administration | Credentials".

How do I troubleshoot WinRM configuration?
Review the article to obtain insight on remote monitoring configuration/troubleshooting.

WindowsAgent or UnixAgent Infrastructure Agent never shows up in Agents on All Hosts dashboard.
Review the WindowsAgent/UnixAgent solution to understand configuration of these agents.

Infrastructure agent not collecting: "Failed to connect" and "a connection could not be established"
Review the article for diagnosing connection failures.

You must restart the computer after you apply this hotfix.