Get Well Knowledge Article
Discovery Pattern Diagnostic Views
An Update Set of Form Views & Related Lists for
Discovery Pattern diagnosis & adjustment
Goal: Locate Discovery Pattern Logs when Show Discovery Events is empty
How this tool can be helpful: The Discovery Pattern Logs are rotated every 90 days, whereas the Discovery Status logs are only kept 30 days
Other benefits to the Diagnostic views include easier access to Related CI types, Pre-post Processing Scripts, Horizontal Probe references and other helpful records
- Locate the “Discovery Patterns Diagnostic View” tool / Update Set attached to this document.
- Download the Update Set and transfer it to the machine accessing the instance.
- Navigate to System Update Sets > Retrieved Update Sets
- Scroll to the bottom of the list, use the Import Update Set from XML to upload the XML.
- Locate the loaded set, Preview it and Commit it.
- Reload the Navigation Window to refresh the menu items.
- Navigate to Pattern Designer > Discovery Patterns – Diagnostic
- Open the application pattern, which in our example is Tomcat
- Shared Libraries must be opened within a pattern which includes it
- Note that we are now in Diagnosis view. If you are not in this view, make sure you followed Step 7 correctly.
- Scroll to the bottom of the form, and switch to the Related CI Types list
- Note / confirm that we see the CI Class where new records sometimes have empty name fields. If we do not see the class name present, it is possible we are in the wrong pattern. (step 8)
- Switch to the Service Discovery Logs related list, and if needed, filter the Managed IP field using the IP Address we made note of earlier when on the host machine Form View.
- At baseline 90 days of records will be available here. This table is managed by Table Cleaner.
Make sure the “View Log” column is at least the third column. View log is a special type of column. Clicking it will open the Discovery Pattern Log viewer. If View Log is not the third column, you should personalize the columns using the gear icon to re-order them.
- Click on “View Log” in the row matching the timestamp for when your Config Item was created without a name. You may have to double-check your creation time stamp, since there might be one or two records here with nearly the same timestamp. (This would indicate Discovery is possibly scanning more than a single IP for the same machine, a topic for another Playbook!) We will confirm in the next section that records were created in this particular instance of the logs. If needed, you can click the Close button to choose another timestamp for review.
|Incorrect View||Correct View|
|If you accidentally open the log entry in regular Form View, you will a regular form view like the one pictured here. If you see this form view, please double-check the Make sure notation for step 12. Use the back button of your browser to return to the Tomcat pattern within Diagnosis view.||With Discovery Pattern Log entry open within the correct viewer, you will see it within a two-pane display shown here. These log entries are in JSON format and you want this viewer to help make them human readable.|
- Once we have the Discovery Log Viewer open as pictured above, please Continue to section titled “With the Discovery Pattern Log open”. (If you came here from another document)