Discovery status is FAILURE

[Community Alums]

Hi Team,

Created customized Application pattern for one of the host and in the debug mode the patterns are successfully, but after i run the discovery against the host, its showing below error:

"Identification Engine: Discovery status is FAILURE, Discovery using patterns failed due to lack of existence of the main CI type in the results. Check the discovery logs for more details."

what could be the reason? and i checked all possibilities.

Any help is appreciated!

Thanks in advance!

[Dnyaneshwaree]

Hello @Community Alums ,

Here are some steps and considerations to help diagnose and resolve this issue:

1. Check Identification Sections

• Main CI Type Configuration: Ensure that the main CI type is correctly configured in the identification sections of your customized application pattern.
• Identification Rules: Verify that the identification rules for the main CI type are properly set up and that they can accurately identify the CI from the attributes collected during discovery.

2. Review Discovery Pattern Steps

• Pattern Debugging: Since the pattern works in debug mode, review the steps in the pattern and ensure they are collecting the expected data during a normal discovery run.
• Data Collected: Confirm that all the data required for identification is being collected by the pattern. You can compare the debug logs with the actual discovery logs to identify any discrepancies.

3. Discovery Logs

• Detailed Logs: Check the detailed discovery logs for the specific host. Look for any warnings or errors that may provide more insight into what might be going wrong.
• Log Levels: Increase the log levels if necessary to get more detailed information about the discovery process and any issues encountered.

4. Main CI Type Existence

• CI Attributes: Ensure that the attributes required to identify the main CI type are being correctly populated. Missing or incorrect attribute values can cause identification to fail.
• Data Completeness: Verify that the data being returned during the discovery process is complete and consistent with what is expected by the identification rules.

5. Pattern Version

• Pattern Updates: If you have recently modified the pattern, ensure that the latest version of the pattern is being used in the discovery process.
• Pattern Deployment: Confirm that the customized pattern has been deployed correctly to the instance where discovery is being run.

6. Service Mapping

• Service Mapping Configuration: If the customized pattern is part of a Service Mapping configuration, ensure that the mapping rules and relationships are correctly defined and are not interfering with the discovery process.

7. Network Issues

• Network Accessibility: Check for any network issues that might be preventing the discovery from accessing the necessary resources on the host.

8. Permissions and Credentials

• Credentials: Verify that the credentials used for discovery have the necessary permissions to access and collect the required data from the host.
• Access Issues: Ensure there are no access restrictions or firewalls blocking the discovery probes from reaching the host.

9. Troubleshoot Step-by-Step

• Step Isolation: Isolate each step in the discovery process to identify where it might be failing. Start by running basic discovery probes and gradually add more complexity to pinpoint the failure point.

If you have checked all these possibilities and the issue persists, you might want to:

• Revalidate the discovery pattern configuration and identification rules.
• Review any recent changes in the environment or host configuration that might affect discovery.
• Reach out to ServiceNow support with detailed logs and configuration settings for further assistance.
  
  

[Community Alums]

Thanks for the info!

I did checked: Application pattern CI Type, its correctly aligned:

Identification Section: all the values are getting populated as expected in debug mode.

IRE: For cmdb_ci_appl, all the values are coming static only matching and able to update, no duplicate record:

Process classification: the table name seems to be correct:

Apart all of this, is there any other table or configuration need to be check?

[Harika K]

I was able to finish "Task: Create iTunes Discovery Pattern (Part 2)," but deviated from the instructions in two ways. Specifically, I chose to use a temporary table, $u_itunes_data, as the target table for the WMI Query step instead of directly using the OOTB cmdb_ci_appl table.

In the Set Parameter step, I used my temporary table's name as the value. For the "Name" field, I dragged the name attribute from the CI Attributes list, resulting in the value $name.

Likewise, repeat in the same way to set Version and Description fields. 

[karthikdsp]

did you complete the next task extended windows server ? if yes pls help me