Bug in SAM Top 10 lists? - Group of Groups limitation not working

lwri

Hi,

We are using NPM 10.4 & SAM 5.2.0 SP1

We have few user accounts which have now limited visibility to nodes by using Group of Groups-limitation.

When testing accounts we found that some of Top 10 view list shows all nodes, not only limited nodes from Groups of Groups-limitation.

This means security risk.

Those wrong functioning Top10 lists came from SAM:

• Top 10 Components by Response Time
• Top 10 Components by Statistic Data
• Top 10 Monitored Processes by CPU Load
• Top 10 Monitored Processes by Physical Memory
• Top 10 Monitored Processes by Virtual Memory

All other Top10 lists were showing limited nodes - those are from NPM.

So, I think this is security bug in SAM Top10 lists or is it feature?

I didn't find any workaround from user editing except using "Group of Nodes" limitation, which means risk of errors when selecting nodes from looong list sorted alphabetically..

My solution is now to drop SAM "Top 10" lists from Top 10 view as they are not functioning correctly.

If you have idea how to solve this, please reply.

aLTeReGo

The Group of Groups limitation was designed to effect only group summary views. It appears as though you're attempting to use groups like custom properties. Groups are for dependency mapping and root-cause analysis. I recommend instead of using groups you look at custom properties, which are far more powerful and were designed specifically to achieve what you're looking to accomplish. The video below should help get you started.

Custom Properties and Account Limitations- SolarWinds Training - Network Performance Monitor - YouTube