Pattern Troubleshooting
This lab explains how to troubleshoot the common Identification Engine problems using REST
and discovery logs.
The lab contains the following sections:
-
Missing dependency -- Destroy dependency rule
-
Troubleshoot - discovery logs and JSON output
-
Fix rule and test rule by executing JSON
Missing dependency / Troubleshoot errors with dependency rule
Navigate to CI Class Manager
Click the Hierarchy button.
Type and Select Whistle in the Search field.
Click Dependent Relationships.
Click the Reset to derived button.
In Confirmation popup window, click Delete.
Rediscover the Bagpipe:
Navigate to Discovery Schedules and choose the Bagpipe Discovery.
Click the Discover now link
When the discovery process ends, click the Discovery Log tab.
Click Here to insert to the pattern log (second row in the table bellow).
Select the Payload Processing link to display the Payload Processing section.
The step failure and the failure reason display the log. In this case, there is missing rule we need to complete.
You can also understand the problem by using the Identification Engine API directly.
Navigate back to the Discovery Schedule page and select the ECC Queue tab.
Open the input record by clicking on the record in the ecc qeueu:
Click the XML button next to Payload to take the Identification Engine payload.
Copy the JSON from items until the end of the JSON without the last "}", as shown below:
Enter REST API Explorer in the Search field:
Click on the green button Explore as seen bellow.
In the API Name, select the Identification and Reconciliation API, and in the Name field, enter ServiceNow as seen bellow**.**
Scroll down to the Request Body field and change the value to Raw.
Paste the JSON you copied earlier and click Send.
Check the response body in the returned payload for the specific error.
The error also appears in the System Error Log; navigate to System Logs System Log Errors.
The same error appears there:
You can fix the error by adding the rule again, as described above.
(You can also use the Metadata Editor to complete the missing dependency.)
