- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-10-2014 03:26 AM
I'm new with Discovery and we are currently we made up and running the Discovery to Development.
My problem is we don't want all Classes to be discovered and like to filter out which classes needs only to be discovered.
Can you help me how ? Let's say below are the items I would like to eliminate classes like:
a. Disk
b. File System
c. Memory Module
d. Print Queue
e. UPS Output
f. Exit Interface Routing Route etc.,
TIA!
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-10-2014 06:54 AM
There are two ways you can do this if you are looking to filter that information:
1) Go into the device classification for the type of CI you are scanning (server, printer ,router, et al) and remove those probes. Most of those probes should be a 1:1 match for the related lists, but some related lists are populated by a multiprobe. You will have to "scan and check" to make sure. This will prevent that information from being populated at all.
2) Alternatively you can simply remove those related lists from the forms themselves and modifying modules and reports where necessary. It's a bit more work initially but allows you to keep all CI information full and up-to-date.
I don't typically recommend removing probes because it can have affects on managing your CMDB outside of eliminating certain types of CIs (ie not utilizing the "running processes" probe prevents discovery from creating and updating CI relationships).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-08-2016 06:44 AM
Id be very cautious in using that configuration console.. very cautious.. a flip of a switch to see what happens modifies the classifier 'behind the scenes' without a save or update option. Once the switch is flipped , the class is Off!
Problem is OOB you cant see other then in that console that you have disabled say Windows Systems when looking at the classifiers themselves.. Unless of course you expose the disabled attribute..