1 Reply Latest reply on Jun 5, 2013 9:57 AM by branfarm

    Monitoring Memory (RAM/Virtual Memory) as a volume?

    Leon Adato

      I have always, as a rule, UN-selected RAM and Virtual memory when choosing which volumes to monitor. I just don't see what I'm going to get from that monitor that I get elsewhere. PLUS, I really don't want to treat my memory resources like a disk. RAM gets fuller faster, changes more rapidly, etc.

       

      Am I missing something? Do you have a compelling reason to include it?

       

      Obviously the amazing engineers at SolarWinds feel this is a good thing to have, since they are selected by default when you discover a node.

       

      Thoughts?