Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Discovery is stsuck at identification phase

konijetisumanth
Giga Guru

Hi All 

 

i am trying to discover the azure vm with ip adress, ports are opned credentials are admin and good, yet the vm is not getting doscoverred rather the discovery log says as below images.

 

ci ia snot getting created in CMDB of servicenow.

 

 

Could you please help me how do i discover the azure vm with ip address. with out cloud discovery.

konijetisumanth_0-1745732157138.png

konijetisumanth_1-1745732197206.png

discovery.PNG

4 REPLIES 4

Gomathi Kannan
Kilo Sage
Kilo Sage

Hi @konijetisumanth ,

 

This may be due to Trigger probes under CI classification record. See there is proper configuration in Trigger probes

 

BR,

Gomathi K

Doci1
Kilo Sage

And what is in the INPUT of WMI runner?

amarkhade
Tera Contributor

Hi, anyone has any findings on this? I am also facing the same issue and not geeting what change we have to make in the identification rule.

Harish Bainsla
Kilo Patron
Kilo Patron

Hi @konijetisumanth  Just check ecc queue classify input payload and below you find credential id and see if it is empty or any value is there