Remove CIs not belonging to application services

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read

    • Remove CIs erroneously mapped as part of an application service by Service Mapping. Unnecessary CIs included in the map can generate irrelevant alerts in Event Management. For example, when creating an application service for a web portal, Service Mapping might automatically discover a connection to unaffiliated external services, such as PayPal.

    Before you begin

    You remove CIs only from application services discovered by Service Mapping.
    Important:
    You cannot fine-tune or edit tag-based and dynamic services from the map.
    Role required: service_mapping_admin

    About this task

    Removing CIs from the map also removes all their connections. For example, if you remove a CI of the second tier on the map, all CIs of the third tier connected to it through outgoing connections, get removed too.

    Depending on why Service Mapping mapped an unwanted CI, you can remove it by the following methods:

    • Add mapping boundaries to remove the unnecessary CIs. A boundary makes Service Mapping stop discovery from this point and not follow outgoing connections. Use this method to remove CIs that Service Mapping discovered using patterns or using traffic-based discovery.

    • Tweak traffic-based discovery. Service Mapping can discover and map configuration items (CIs) following their traffic-based connections. This method is referred to as traffic-based mapping and complements pattern-based mapping. Service Mapping generates connection suggestions based on traffic-based connections and on Predictive Intelligence analysis of application fingerprints. If the connection suggestions feature is enabled, Service Mapping doesn't automatically add any traffic-based connections to application services, providing suggestions. Review the suggestions and choose which CIs to add or to remove.

      If the connection suggestions feature is disabled, Service Mapping automatically adds traffic-based connections and CIs to application services. Remove connections that lead to irrelevant CIs to declutter application services.

    Procedure

    1. Open the service instance map.
      1. Navigate to All > CSDM > Manage Technical Services > Service Instance.
      2. Select the needed service instance.
      3. On the service instance page, select View Map.
    2. Remove CIs that do not belong to this service instance by completing the following actions.
      Action Steps
      Add mapping boundaries
      1. Right-click the connector leading to the CI you want to remove.
      2. Select Mark boundary.

        The CI is marked as boundary on the map (The boundary icon).

      Note:
      Ensure that you are looking at the map in Edit view.
      (If the connection suggestions feature is disabled) Remove CIs discovered using traffic-based connections
      1. Right-click the CI on the map.
        Note:
        You can see traffic-based connections for a CI, even if you disabled the traffic-based discovery for an service instance the CI is part of.
      2. Select Show traffic based connections.

        The Traffic Based Connections List opens. See Traffic-based connections list.

      3. In the Traffic Based Connections List, identify the connection used to discover the unwanted CI.
      4. Select Remove from the User decision field for this connection.
      5. Click Close.
      (If the connection suggestions feature is enabled) Remove CIs discovered using traffic-based connections Perform the procedure described in Add or remove CIs for single application services using connection suggestions.