Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Skip errors to continue discovering an application service

Log in to subscribe to topics and get notified when content changes.

Skip errors to continue discovering an application service

If you know what configuration items (CIs) and connections make up your application service, you can enable Service Mapping to continue discovery of the application service even if there are some errors. You can skip errors to troubleshoot later so you can complete mapping most of the application service, even if some CIs are missing.

Before you begin

Familiarize yourself with the structure of the application service to know which CIs make up the next tier after the problematic CI. If necessary, consult the application service owner to collect necessary information.

Role required: sm_admin or admin

About this task

Normally, discovery of an application service stops when Service Mapping fails to identify a CI. In this case, the map shows a warning icon instead of the undiscovered CI. There are no CIs or connections going out of the undiscovered CI.


Example of an undiscovered CI on the map.

You can overcome the obstacle of the undiscovered CI and restart discovery from the CIs belonging to the next tier after the problematic CI. To do so, add a CI manually if you know what the undiscovered CI is and what the incoming connection of the next tier CI is. Service Mapping uses incoming connections to access a CI for discovery. These connections are referred to as endpoints.

Procedure

  1. Navigate to Service Mapping > Services > Application Services.
  2. Click View map next to the application service that you want to view.
  3. Ensure that the map opens in Edit mode.

    When you click Edit, the Discovery Messages section appears below the map.
  4. Ensure that the map is not in the Host View.
  5. Click the arrow next to the undiscovered CI and select Skip and Resume.
  6. Define attributes of the CI you want to manually place instead of the undiscovered CI.
    Field Description
    CI Type Select the CI type (CI class) for the CI you are adding. Every CI belongs to a CI type which contains a set of attributes configured for this kind of CI, for example, cmdb_ci_appl for applications.
    CI Name Select the CI from the list of CIs of the selected CI type.
    Note:

    If the CI type does not appear in the list, Service Mapping does not allow adding CIs of this type manually. For example, you cannot add an application cluster or an endpoint manually.

  7. Configure attributes of the entry point from which Service Mapping continues discovery by selecting the entry point type and entering relevant fields.
    If the required entry point type does not appear in the Select Entry Point Type list, create it as described in Create entry point types for Service Mapping.
  8. Click Submit.
    The map shows the manually added CI instead of the undiscovered CI. Service Mapping starts discovery for CIs of the next tiers. When the discovery process finishes, the map shows all discovered CIs below the manually added CI.

    Example of result of skip and resume

What to do next

To discover the problematic CI automatically:
  1. Perform necessary troubleshooting to enable Service Mapping to discover the problematic CI. For example, you may need to customize the relevant pattern, provide missing credentials or fine-tune traffic-based discovery.
  2. Navigate to the relevant application service map.
  3. Click Run discovery.
  4. After the discovery process finishes, verify that Service Mapping discovered the CI. If Service Mapping discovered the CI, the map shows the actual CI without the Warning icon (The Warning icon).
Feedback