The SolarWinds Agent provides a robust alternative to agentless polling (SNMP/WMI), particularly in restricted environments. According to the SolarWinds Platform Agent requirements and port information , the primary architectural benefit is its communication security and firewall-friendly nature.

When using an agent, communication is consolidated. Instead of requiring a wide range of dynamic ports for RPC (as with WMI) or multiple ports for various SNMP checks, the agent communicates through a single fixed port (typically TCP 17778 for agent-initiated or 17790 for server-initiated communication). Furthermore, all traffic between the agent and the polling engine is encrypted using 256-bit AES encryption. This makes agents the ideal choice for monitoring:

DMZ Servers : Where opening numerous ports back to the management network is a security violation.

Cloud Instances (AWS/Azure) : Where data must travel over public or semi-public links and requires encryption in transit.

Remote Sites : Where NAT or strict firewall rules make traditional SNMP/WMI polling impossible.

Option B is incorrect because agents still report back to the Polling Engine (Orion Information Service), which then handles the database writes. Option C is incorrect as the agent actually increases the granularity of data collection, which may slightly increase database volume rather than reduce load.

PerfStack is a cross-stack data correlation tool, but its visibility is constrained by the underlying data collection modules and user security settings. According to the PerfStack Troubleshooting Guide , there are two primary reasons why specific entity data (like Storage) would be missing:

Product Not Installed : Performance data for deep storage metrics (like LUN latency, Array IOPS, or Pool capacity) requires the Storage Resource Monitor (SRM) module or the equivalent HCO storage licensing tiers. If only Server & Application Monitor (SAM) is installed, the user will see the application status, but the specific storage back-end metrics will not be available for selection in the PerfStack pallet because the "collector" for that data doesn't exist.

Account Limitations : SolarWinds uses Account Limitations to restrict user access to specific parts of the infrastructure. If a user account is limited to "Department = Sales" or "Vendor = Cisco," and the storage entities do not meet those criteria, those entities will be filtered out of the search results in PerfStack. Even if the data exists in the database, the platform security layer prevents the user from "finding" or displaying it to ensure data privacy and multi-tenant security.