PLEASE PLEASE PLEASE
On the next version rework the import/discovery process , right not it is the most painful part of any SolarWinds product by far.
What is it that you dislike the most about it?
--Christine
Well without trying to sound sassy most of it.
If I had 100 nodes to put in it it would be fine. But I have a few thousand I want in it not to mention the thousands it finds I do not want.
This is how I think it should work. I know there are round about ways to do this and I have tried and they are painful and error prone and very manual.
Step 1) Add SNMP strings - good implementation
Step 2) Discover subnets - good implementation
Step 3) Select Subnets - when you have about 1500 of them the way it works now is a pain
Step 4) The discovery process - good implementation
Step 5) Select nodes to import - this is the most painful portion. If it finds 4000 nodes and I needs to select 2000 then I sit in front of a keyboard for ever in a very error prone process
Now a trust worthy scheduled discovery would be awesome. IE one that does not add duplicates and only adds nodes based on certain criteria like vendor = cisco or machine types x, y and z etc.
Definitely number 5, I've given up using the discovery process because of HOW cumbersome it is to use, if it could be automated like the NPM discovery but would only import criteria based devices and exclude duplicates that would be perfect. At the moment I manually add mine and it takes forever but is easier and quicker than using the discovery process in NCM.
Ok - thank you all for your feedback. I'll get these requests documented. Discovery is on our road map to get some attention, so this feedback is well-timed.
