I just wanted to get a feel for other users to see if they are having the same hardships as we are.
Since 10.7 we have been plagued with "Long Running Query" issues. These typically get addressed with "Buddy Drop" fixes... but future upgrades had the same issues (requiring new Buddy Drops). Every time we would upgrade, we would have massive performance problems until these fixes were addressed by development (sometimes weeks later).
We are a large retailer with many stores and we organized them by group when we initially set up SolarWinds.
We've come to realize that this was a really bad idea and we are in the process of rethinking how we have everything organized because NPM doesn't seem to be coded to accommodate this mentality by default (although there are options for it).
You would THINK it would be a really organized to group this way...
(node) Switch 1
(node) Switch 2
(node) Router 1
(node) Router 2
(node) Register 1
(node) Register 2
(node) Register 3
Back Office Workstation
(node) Device 1
(node) Device 2
(node) Server 1
(node) Server 2
How we saw it, was we could build dashboards and have them view limit based off of "group of groups" and get all the data we care about.
This turns out to be a horrific idea because of how NPM queries things... It doesn't play nicely with nested groups (causing these long running query problems).
SolarWinds developers would prefer you use a completely flat group for all of your stores and put all of your store equipment into that folder for maximum performance.
Does anyone else use lots of groups or lots of nested groups? Are you having the same performance problems we have when trying to use view limitations based off of "group of groups"?
I'd love to hear your thoughts if you have the time.
Thanks in advance.