Tag-based discovery configuration

You can refine the default configuration to control which CIs Service Mapping includes in application services during the tag-based discovery process.

Starting with Service Mapping Plus version 1.16.3, take advantage of the Tag-based Service Mapping workspace to efficiently map you application services. For more information, see Tag-based mapping in the Service Mapping Workspace and Tag-based discovery for the Service Mapping Workspace.

Service Mapping provides preconfigured CI relationships which can participate in tag-based discovery. You have the ability to customize these CI relationships and refine the default configuration using one of the following methods:

• include CIs based on classes in tag-based discovery;
• exclude CIs based on their install status;
• exclude preconfigured CI relationships;
• add or edit CI relationships.

To view preconfigured CI relationships which Service Mapping includes in application services during tag-based discovery, see Preconfigured CI relationships in tag-based discovery.

To view properties installed with Service Mapping that relate to tag-based discovery, see Properties related to tag-based discovery.

• Include CIs based on classes in tag-based discovery
  Use CI classes to identify which CIs Service Mapping includes in application services during tag-based discovery. By default, this list appears empty and includes all CIs belonging to all CI classes. Define CI classes and allow only CIs belonging to these classes or their extensions to participate in tag-based discovery.
• Exclude CIs based on their installation status in tag-based discovery
  Use the CI installation status to create CI classes and exclude CIs from application services during tag-based discovery. By default, application services based on tags exclude CIs with the Retired or Absent install status. You can expand this list of excluded CIs to include additional installation statuses such as Pending install or Stolen.
• Exclude preconfigured CI relationships in tag-based discovery
  Exclude preconfigured CI relationships from the tag-based discovery process to refine the application services created. Service Mapping consists of preconfigured CI relationships and includes CIs in these relationships even if they do not have assigned tags. Choose which preconfigured CI relationships to exclude and the remaining CI relationships participate in tag-based discovery.
• Add or edit CI relationships in tag-based discovery
  Activate pre-configured CI relationships that Service Mapping does not include by default or add additional relationships to use in the tag-based discovery process. For example, you can add a CI relationship between Linux servers and storage devices to discover servers hosting storage devices based on tags.
• Recalculate previously created application services
  Recalculate application services after you refine the default configuration to control which CIs to include during the tag-based discovery process.