Configure Discovery to stop after classifcation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2017 01:45 AM
In the documentation for creating a discovery classification. It says that it is possible to configure discovery to not trigger the specified exploration probes:
Triggers probes | Select the exploration probes you want Discovery to launch. These probes gather detailed information about a classified CI. Discovery will not launch these probes if it is configured to stop after classification. If you want to use patterns for horizontal discovery, add the Horizontal Pattern probe in the Probecolumn, and then specify your pattern in the Pattern column. Warning: Do not specify your pattern in Probe column. You must chose the Horizontal Pattern probe, which launches the specified pattern. |
I cannot find any documentation on how to configure discovery not to launch probes after classification. Does anyone know how to do this? I'm hoping there is a property, rather than me having to individually disable each discovery_classifier_probe record.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2017 02:40 AM
Hi Kieren,
I am not sure it is possible to remove some probes in Discovery apart removing from the classification record. If you don't want to run some specified Exploration probes then you can remove it in the particular classifier record. That will be in the below location
Discovery Definition --> CI Classification --> CIM/Windows/Unix
For an example, the above screenshot is Windows 2008 Server classification record. Inside you can see 19 trigger probes, these probes will get triggered when Discovery classifies Windows 2008 server. you can press edit to remove or add new probes.
Regards,
Vivek
Based on the impact hit like, helpful or correct
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2017 02:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2017 02:55 AM
Hi Kieran,
Not sure it is what you need but you can use the Discovery configuration console to disable discovery of some devices/applications. If for example, you want to discover Windows servers but not workstations, you can switch off the 'Windows Computers'. In this case, because you are not switching all Windows off, if will still attempt to classify (and therefore authenticate) with the computers but it will not send the identification probe (or any other probe) and you will see a message in the logs similar to 'Classified but disabled'
Regards,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2017 12:04 AM
The way I've ended up doing it is setting active = false for all of the discovery_classifier_probe records.
This is the query I used to switch the ones I didnt want to run off:
var pc = new GlideRecord('discovery_classifier_probe');
pc.addQuery('phase', 'exploration');
pc.addQuery('classy.sys_class_name', 'discovery_classy_proc');
pc.addQuery('active', 'true');
pc.addQuery('classy.name', 'DOES NOT CONTAIN', 'Pending:');
pc.query();
pc.setValue('active', false);
pc.updateMultiple();