Traffic-based discovery in Service Mapping

Service Mapping uses traffic connections to collect network statistics and perform traffic-based mapping.

The major way of Service Mapping collecting data is by using patterns. However, Service Mapping can also discover CIs by following traffic connections between CIs. This method is referred to as traffic-based discovery.

Using traffic-based discovery is like casting a finer net, allowing Service Mapping to find even those CIs that it failed to discover using patterns. The advantage is discovering more CIs, at the same time this method may clutter a business service with irrelevant CIs. Typically, you use traffic-based discovery at the initial stages of discovering a business service and disable it once you completed discovery and fine-tuned the business service.

Service Mapping detects inbound and outbound connections using the netstat and lsof commands.

You can enable traffic-based discovery at different levels listed here from the most global to the most specific:

  • Product level

    By default, traffic-based discovery is enabled in Service Mapping allowing it to use this method at all levels.

  • Business service level

    As part of defining a business service, you can enable traffic-based discovery for it. In this case, Service Mapping uses this method for all CIs making up this business service, unless traffic-based discovery is disabled for some CI types or specific CIs.

  • CI type level

    You can create a discovery rule to include or exclude a CI type from traffic-based discovery. This rule prevails over the setting you choose for a business service.

  • Specific CI level

    You can create a discovery rule to include or exclude a specific CI from traffic-based discovery. This rule prevails over the setting you choose for a business service.

    Rules for specific CIs take precedence over rules for CI types. For example, if you do not want to use traffic-based discovery on any Tomcat servers, you can define a CI type rule disabling the traffic-based discovery on the Tomcat table. At the same time, you can create a discovery rule enabling the traffic-based discovery for a specific Tomcat server. In that case, Service Mapping uses the traffic-based discovery only for this specific Tomcat server out of all Tomcat servers.


CIs displayed on the map.

While using traffic-based discovery creates a more inclusive map, it may also result in mapping many redundant CIs that do not influence the business service operation. You can choose to hide CIs discovered using this method from a business service map. In that case, these CIs are still part of the business service, but they are not on its map.