Agent Driven Inventory Discovery

I activated the Agent Driven Inventory Discovery job, however no CI's were automatically added to the triggered CI list.  When I manually added a UDA CI it failed with the following message:

"Server Processing Failure / Probe wasn't found for this CI.  Failed to parse probe name from override domain text"

Is there a setup step I missed? what is the override domain text?

Not sure where to go from here

Thanks

  • Hello ,

     

    Filter those CIs which associated with IpAddress having no probe name in trigger TQL.

     

    Regards,

  • Discovery Probe Name should not be null on UDA CI. Not sure which job will populate that attribute.

  • I'm having the same issue that the UDA CI type does not have the Probe Name value set. I have run the Host Connection by Shell, UDA Status Collector, and Range IPs by ICMP. None of these jobs populate the Probe Name value.

    How have you fixed the issue?

  • Try this:

    Go to the job, (Universal Discovery, Discovery Modules/Jobs) - find the job (Host Connection by Shell for instance).  Go to the Properties tab of the job.  

    Under Trigger Queries, see if host_shell (or whatever is located there) has <<All Probes>> on probe limit.

    My bet is they say <<Disabled>>.  Click on the icon with the three dots and select "ALL PROBES".

    Save and re-run.

  • Try this:

    Go to the job, (Universal Discovery, Discovery Modules/Jobs) - find the job (Host Connection by Shell for instance).  Go to the Properties tab of the job.  

    Under Trigger Queries, see if host_shell (or whatever is located there) has ((All Probes)) on probe limit.

    My bet is they say ((Disabled)).  Click on the icon with the three dots and select "ALL PROBES".

    Save and re-run.

  • thank you for the suggestion. The job Host Connection by Shell runs and updates attributes on the UDA CI but it doesn't populate the attribute Discovery Probe Name.

  • I would be interested in your input on this issue. Do you know what job will populate the attribute Discovery Probe Name on the UDA CI? This attribute is required for the trigger TQL of Agent Driven Inventory job.
    ADID_Trigger_TQL.png

    For reference see the Agent Driven Inventory Job in content pack documentation.

  • Hello John,

     

    I've encountered the same problem in the past.

    It's not a problem to populate the uda_probe_name attribute (known as Discovery Probe Name) as we can send it though the dispatch mechanism of HostConnection by shell and model it.

    The real problem is what we do with flying devices? Those devices that often change their network location and will have to report to different probes.

    I can't make a simple script patch for this and you can test it. What's your CP version?

     

     

  • Hi,

     

    In this case I think that it is exactly the problem of not populating UDA's uda_probe_name attribute. 'Agent Driven Inventory Discovery Adapter', 'Advanced Agent Driven Inventory Discovery Adapter' and 'Basic Agent Driven Inventory Discovery Adapter' all have it as 'Override default probe selection'. And even if this attribute is ignored by the dispatch mechanism, then the trigger TQLs are not feeding UDA CIs to the job, since they have it as requirement in the statement as John stated. 

    I've checked all the python script sources connected with Host Connection by Shell, the job which should be able to provide a value for it, but nowhere uda_probe_name is mentioned. This attribute seems to be a ghost from the past.

    Regards,

    Petko

  • I will open a support case. As has pointed out, this workaround will not solve the issue that there is no current way to trigger this job since there is nothing populating Discovery Probe Name.

    I am curious if anyone has this discovery job working at all. This has been available since 10.3x or 2018 when started this topic.