Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Remove CIs not belonging to business services

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

Remove CIs not belonging to business services

If Service Mapping erroneously mapped some CIs as part of a business service, remove these CIs for noise reduction. It is important to remove unnecessary CIs from the map, because they can generate irrelevant alerts in Event Management. For example, when creating a business service for a web portal, Service Mapping may automatically discover a connection to external services, such as PayPal, that do not belong to the service.

Before you begin

Role required: sm_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 uses traffic-based connections to collect network statistics and perform traffic-based discovery. This discovery method may clutter a business service with irrelevant CIs. Service Mapping uses an algorithm to reduce the number of erroneously mapped CI. You can further adjust traffic-based discovery to remove unwanted CIs.


  1. In the child instance,navigate to Service Mapping > Services > Business services.
  2. Click View map next to the relevant business service.
  3. To remove CIs, right-click the connector leading to the CI you want to remove, and select Mark boundary.
    The CI is marked as boundary on the map (The boundary icon).
  4. To remove CIs discovered using traffic-based discovery, perform the following steps:
    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 a business service the CI is part of.
    2. Select Show traffic based connections.
      The Traffic Based Connections List opens displaying the following information:
      Table 1. Traffic Based Connections List
      Field Description
      IP The IP address of the application connected to the selected CI.
      Port The port on the selected CI that is used to communicate to the other application.
      Process The ID of the process in the selected CI.
      Already on map
      • Yes — if this connection shows on the map.
      • No — if this connection is not part of the business service and not on the map.
      System decision The setting defines if Service Mapping keeps the discovered traffic-based connection or removes it. The value comes from the algorithm that Service Mapping uses.
      User decision (Optional) The setting overrides the System decision setting, which defines if Service Mapping keeps the discovered traffic-based connection or removes it. For example, if the System decision setting for a connection is Keep, and you want to remove this connection, select Remove.
      Note: There may be a case when you can see traffic-based connections on the map, but the Traffic Based Connections list does not display them. It happens for the connections that have been removed from the TCP Connection [cmdb_tcp] table less than three days.
    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.