Curious what symptoms others have experienced that indicated the need for an additional APM poller?
A few more would be server resource exhaustion (CPU/Memory) or unusual/unexpected/sporadic component monitor timeouts usually resulting in component monitors showing an "Unknown" status.
Hi,
if there are gaps in report data but there is lots of RAM and even more CPU resources left, would that indicate the need for an additional poller?
if so, what exactly is the reason for this?
I've seen this occur when maintenance runs or backups are running on the SQL server. Anything that causes extremely high I/O on the SQL server database (tempDB or NetPerfmon database). If this is a shared SQL server other applications using the database server could be having a negative effect on the performance of the SQL server. Resource exhaustion on the SQL server is always a possibility. If we collect the information but are unable to store it in the database in a timely fashion then it doesn't make it into the database. This results in gaps in the data.
I've also seen customers who are polling across WAN links experience timeouts due to network high latency.
These are some of the more common places to start looking.
helpful stuff.
Would incorrect polls per second tuning also end in gaps?
The polls per second tuning tool tweaks settings inside the standard poller which APM does not rely on for polling beyond standard CPU/Memory node information. All component monitors within the APM product use the collector/business layer host for polling which are not effected by the Polls Per Second tool.
I am asking because we experience "slow polling" or gaps with APM, we have enough RAM, enough CPU, no disk queue, low latency on the drives, etc.
We have about 3000 monitors on APM.
SQL is running on the same server as network connectivity issues have been suggested as the problem several times by solarwinds staff. SQL is running on a RAID as suggested by solarwinds but we still experience "gaps"