A user is building a PerfStack project to troubleshoot an issue with an application.

PerfStackis a cross-stack data correlation tool, but its visibility is constrained by the underlying data collection modules and user security settings. According to thePerfStack 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 theStorage 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 usesAccount Limitationsto 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.