Adding a new probe and including in it Discovery Schedule.

shanushaan
Kilo Explorer

I have made a new SSH command probe for LINUX Discovery and individually tested it using TEST probe.
The probe is working fine with all the details.
But if I run the complete Discovery the probe is not getting added in the complete Discovery Schedule.
What am I missing ??

5 REPLIES 5

doug_schulze
ServiceNow Employee
ServiceNow Employee

Have you included it in the Linux classifier? Discovery definition > (ci classification group) > unix > linux...

Click edit in the triggers probe section and add it there...


prdelong
Kilo Guru

Did you include the probe in the proper classifier? I'm assuming you want to use it in on a Unix/Linux server. You need to go to the 'Unix' module under CI classifications. Find whichever classifier you want to launch and click into into. There should be two related lists at the bottom - 'classification criteria' and 'triggers probes.' Hit the edit button on the 'triggers probes' related list and you should see the name of the probe you want to launch. Make sure you set it to the proper phase, most likely exploration, once the probe is triggered by the necessary device classifier. Once it has been added there, the probe should be launched with the rest of the OOB probes once the Unix classification criteria has been met during the Unix classifier probe. If you need or want to create a separate classification for a specific platform, follow the directions in the Wiki article below.

http://wiki.servicenow.com/index.php?title=Discovery_Classification_Parameters


Thanks Doug,
I have a lifetime of 2 days in this tool and started to like it very much. Thanks for the quick response.

Rohit


Very cool! Glad to be of service, please (if you'd like), don't forget to share what custom probe/sensor you added to our community here... you never know who may find value in it... sharing is caring!