This is a rough draft below of an idea I thought to be valuable. I'm accepting input below from anyone who wishes to contribute. I would like to mature this idea in hopes of catching the eyes of the product managers and or developers from solarwinds. I'm hoping possibly to get some traction on this if the community things this is something useful.
This idea stems from having a large environment and not having an easier way to load balance jobs and devices across all pollers.
1. When you do a discovery, the poller always defaults to one single poller. Discovery should be set to add devices across pollers depending on poller load. This way for those unaware, they won't be overloading just a single server when they do not change the poller before starting the discovery. I myself have many times while going through many discoveries forgotten to change the poller causing everything to be added to my primary overwhelming and overloading my primary server. I think discovery should have two modes an auto mode that will automatically let the devices be distributed and added evenly or a manual mode where you chose the poller where you want to add the devices too. This will enable ease of use when adding devices so that they are even displaced among the pollers instead of crashing a server with to many devices to be monitored.
2. This would be good if it could be implemented with other modules in consideration. For example, right now I have one poller with 250 devices which is low on device count. but when you add templates, interfaces, volumes, etc. Once can easily see that even with a small node count you can still overload the servers without knowing it.
We have near 100k element count and quickly growing. Due to no inventory list telling me which node is where and what is being monitored my environment is all over the place which means I have to take time to go through this even things out which will not at all be an easy task.
I'm sure those with large infrastructures will appreciate this idea and I'm hoping people will contribute more to it. It is something I think could potentially bring even more value to solarwinds.
This is a tool and or function already offered in some competitor software. I think it would put solarwinds ahead of them having such a tool in place.