Monitoring Qumulo or Unsupported Storage Vendors in SRM

jthompsonjr2

Hi everyone,

Does anyone have experience monitoring Qumulo File Share with SolarWinds SRM?

More broadly, what is the recommended approach for monitoring storage platforms that are not listed as supported SRM vendors? Have you had success using SNMP, REST APIs, SAM templates, custom pollers, or another method?

mr.castaneda

SolarWinds SRM currently provides array‑level monitoring only for vendors that are on the supported SRM storage matrix (arrays you can add via the Add Storage Device wizard in the Storage Summary view). Qumulo is not yet a natively supported SRM storage array, so it can’t be added and modeled in SRM the same way as NetApp, Dell, HPE, etc.

That said, there are a couple of practical options you can use today:

• Monitor Qumulo via SAM / custom pollers
  • If Qumulo exposes metrics over SNMP or a REST API, you can build SAM templates or custom pollers to collect health and performance data (CPU, memory, disk usage, throughput, latency, etc.) from the Qumulo cluster or its front‑end nodes.  
  • Those SAM or poller metrics can then drive alerts, dashboards, and reports alongside your other SolarWinds data.
• OS‑level monitoring of Qumulo front‑end systems
  • You can also monitor the servers or virtual machines that front Qumulo (services, processes, volumes, network, etc.) with SAM or SWOSH for basic availability and performance visibility.

These approaches give you good operational visibility, but they don’t provide the full SRM storage‑array model (pools, LUNs, end‑to‑end storage topology). For that, we’d need native SRM support for Qumulo.

If this is important in your environment, I’d recommend opening or upvoting a feature request for “Native SRM support for Qumulo storage arrays” so Product Management can track demand and prioritize it on the SRM roadmap.

Hope this information is useful.