A polling engine is a polling engine and it doesn't care if your technologies are split or not. You just want to make sure none of yours are above 100%, and ideally 85% (to allow for resource growth, etc for example when you add SAM). If you have all of your Windows Servers though on a single PE and it is at 87% chances are once you add SAM app monitoring you will be far above 100% so sounds like you will need to split up your servers (definitely Windows, and probably Linux) across APE 3.
I know all of that, I'm looking for an algorithm or strategy that will keep the load balanced. The first goal is to balance the polling load, a secondary goal is to take remove decision making from the process, so that I can document how to add nodes to Solarwinds without there being any ambiguity in how it's done. Right now, selecting the polling engine is a not a clear-cut process that I can document and hand off to junior tech's to use for adding nodes.
The strategy is to fill up APE 1 until that is as full as you would like to make it, and then move on to APE 2 and so on. It doesn't matter if you have servers spread across different PE's and co-mingling Windows and Linux. Your junior techs should be adding everything to highest numbered APE, and as soon as APE 3 fills up you create APE 4 and they use that one.
2 of 2 people found this helpful
Ideally you want to mix your type of load across the polling engines so you can shift load around at will rather than being dependent on one particular servers for any particular load.
the module engine aka BusinessLayer can be configured to run a separate process for each type of polling; you MIGHT want to take advantage of that if you are in a very large environment. However this adds a layer of complexity that most sites don't need, and is only needed if you're running servers at the limits of their performance, and I would not worry about it until then (as there are other things to be concerned about).
Our process here is to add all new stuff to the main server, and then about once a month move all of the polling load from that server off onto the least loaded APE. This allows us to check out anything new/odd/unusual with new equipment easily and balance load across the other servers. it also keeps the polling load on the main engine light which improves performance of the webUI and other components that only run there.
Here are two of my polling engines; note that one of them as a much higher Wireless polling rate than the other (because it happens to have more wireless controllers on it)
Polling Completion 99.99
Network Node Elements 2198
Volume Elements 63
Interface Elements 7281
Routing Polling Rate 1% of its maximum rate.» Learn more
UnDP Polling Rate 0% of its maximum rate.» Learn more
Hardware Health Polling Rate 25% of its maximum rate.» Learn more
Wireless Polling Rate 1% of its maximum rate.» Learn more
F5 Polling Rate 0% of its maximum rate.» Learn more
Polling Rate 42% of its maximum rate.» Learn more
Total Job Weight 4075
Network Node Elements 2175
Volume Elements 0
Interface Elements 6799
Routing Polling Rate 0% of its maximum rate.
UnDP Polling Rate 0% of its maximum rate
Wireless Polling Rate 13% of its maximum rate.» Learn more
Hardware Health Polling Rate 21% of its maximum rate.» Learn more
Polling Rate 40% of its maximum rate.» Learn more
Total Job Weight 4240
It looks like the way to go is to add to the lowest number server until you hit the 85% mark, then load up the next.
Something I noted above is that I am monitoring network drives because they were selected by default during discover/import process. Is there a way to 'unmonitor' network drives in batches? Since we have thousands of servers, doing it one node at a time would take a very long time to complete.