How do you load balance SAM Polling?

Is there a well-defined process for load balancing SAM polling? I recently enabled AppInsight for Exchange. With around 60 servers,SAM Application Polling Rate jumped from 0% to over 200% utilization. The funny thing is that I moved the Exchange servers to another polling engine, and then SAM polling utilization only went down to 175%.

SAM Application Polling Rate

172% of its maximum rate.Polling intervals increase if the polling rate exceeds 100% of the maximum rate.Add Poller » Learn more

While I'd love for Solarwinds to have load balancing algorithms built into the software, I don't think that feature is coming any time soon.

In the meantime, what is the recommended way to manage the polling load?

In a related question, is there way to see how much each node "weighs" down the polling engine so that I can identify the ideal nodes to move to another polling engine?

Find more posts tagged with

apinsight for exchange

load balancing

server and application monitor

Accepted answers

All comments

codyb

Did you get an answer to this?

jrouviere

SAM scaling is 10,000 components and 12,000 elements (as with NPM) per poller.

Scale SAM for larger environments - SolarWinds Worldwide, LLC. Help and Support

You can review your current component counts by going to Settings -> All Settings -> Database Details and clicking on Total Elements per Poller at the very bottom of that page.

Total element per Engine Count SQL Query - SolarWinds Worldwide, LLC. Help and Support

There are several reports around Thwack that work to provide this information, but all of them return differing numbers and I was told by Support that this was the definitive measure.

There is a way to report on components per node, but I built it myself in SWQL and don't have the query readily available.

Also worth mentioning that we had 2-3 times the component count and our polling load was not reflective of that at all, we were told by Support that the percentage of polling load wasn't a good metric to use, but component count was the real measure.

borgan

Even three years later, i would still like to see this query. I am still looking for a way to know how many SAM components will be moved when I move a node to a different polling engine.