Appliation Discovery Very Very Slow

Yesterday I started an application discovery for about 150 servers looking for one application, specifically the SQL 2005 - 2008 Performance (WMI) template from SolarWinds. Today when I arrived at work 12 hours later it was less than half way completed. I realize that WMI is slow and that it takes time to test each of the logins (I have 4 that it tests for); however, this seems excessively long.

One thing I noticed is that it seems to only scan one node at a time, is it not possible to allow APM to do some parallel scanning to make it move along a bit faster on these?

Any input, thoughts, comments, etc would be appreciated!

Find more posts tagged with

Accepted answers

All comments

mcbridea

At this point that is too many servers to scan in one job. I would break it up into 20 servers max at a time.

byrona

At this point that is too many servers to scan in one job. I would break it up into 20 servers max at a time.

Well, it's still scanning and hasn't appeared to break anything, it's just taking forever. In my environment of over 500 nodes I kinda sorta need something that can handle more than 20 at a time.

aLTeReGo

The Application Discovery time is based on the number of templates that are being tested and the number of nodes selected. Since every component monitor in each selected template is tested against every node in the list I would recommend reducing the number of templates or the number of nodes in the application discovery process.

byrona

So, it looks like that discovery did encounter problems. I started to see a bunch of "Canceled by Scheduler" issues.

Going forward it would be nice to see a bit more beef put behind this mechanism and maybe some parallel discovery to allow it to scan for a lot more stuff, otherwise this feature is mostly useless in larger environments.