Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Operations Management
Table of Contents
Choose your release version
    Home Orlando IT Operations Management IT Operations Management ITOM Visibility Service Mapping Advanced Service Mapping configuration Configure tag-based discovery

    Configure tag-based discovery

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Configure tag-based discovery

    Fine-tune the default configuration to control which CIs Service Mapping includes in application services during tag-based discovery.

    Before you begin

    Learn about the default feature configuration covered in Tag-based discovery in Service Mapping.

    Role required: sm_admin

    About this task

    Control which CIs can become part of application services in the following methods:
    Include CIs based on classes
    Define the CI classes to allow only CIs belonging to these CI classes or their extensions to participate in tag-based discovery. By default, this list is empty and CIs belonging to all CI classes are included in tag-based discovery.
    Exclude CIs based on their install status
    By default, CIs with the Retired or Absent install status are not included in application services, based on tags. You can broaden this list of install statuses to include statuses like Pending install or Stolen, for example.
    Modify CI relationships used for tag-based discovery
    Service Mapping includes CIs that are part of these relationships even if these CIs do not have tags assigned to them. The CI relationships participating in tag-based discovery are stored in the Application Services [svc_traversal_rules] table. You can exclude preconfigured CI relationships from tag-based discovery. You can also configure additional CI 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.
    Note: You cannot delete or modify preconfigured CI relationships used for tag-based discovery from the Application Services [svc_traversal_rules] table.
    Table 1. Preconfigured CI relationships participating in tag-based discovery by default
    CI Relationship CI
    Virtual Machine Instance [cmdb_ci_vm_instance] Virtualized by::Virtualizes Hardware [cmdb_ci_hardware]
    Hardware [cmdb_ci_hardware] Runs::Runs on Application [cmdb_ci_appl]
    Kubernetes Pod [cmdb_ci_kubernetes_pod] Contains::Contained by Operating-system-level Virtualization Container [cmdb_ci_oslv_container]
    Note: Service Mapping user interface refers to CI classes as CI types.

    Procedure

    • To include CIs based on classes, perform these steps:
      1. Navigate to Service Mapping > Administration > Properties.
      2. Enter CI classes separated with a comma in the svc_by_tags.classes.whitelist property field.

        Define CI classes to control which CIs participate in tag-based mapping.
      3. Click Save.
    • To exclude CIs based on their install status, perform these steps:
      1. Navigate to Service Mapping > Administration > Properties.
      2. Enter values for install statuses using a comma to separate these values in the svc_by_tags.install_status.blacklist properties.

        Define install statuses to exclude CIs with these statuses from the tag-based discovery.
      3. Click Save.
    • To exclude preconfigured CI relationships from tag-based discovery, perform the following steps:
      1. Navigate to Service Mapping > Administration > Tag-based Service Traversal Rules.
        The Application Services [svc_traversal_rules] table appears filtered to show only CI relationships used for tag-based discovery. Preconfigured CI relationships, used in tag-based discovery by default, have the true value in the Base System Rule column.

        Table containing information on CI relationships used in tag-based discovery.
      2. Click the preconfigured CI relationship you want to exclude from discovery.
        The Traversal Rules for Application Services form opens.
      3. Clear the Active check box.
      4. Click Submit in the Traversal Rules for Application Services form.
    • To add a CI relationship or edit an existing CI relationship that is not preconfigured, perform the following steps:
      1. Navigate to Service Mapping > Administration > Tag-based Service Traversal Rules.
        The Application Services [svc_traversal_rules] table appears filtered to show only CI relationships used for tag-based discovery. Preconfigured CI relationships used in tag-based discovery by default have the true value in the Base System Rule column.
      2. Click the existing CI relationship you want to modify or click New to use an additional CI relationship in the tag-based discovery process.
        The Traversal Rules for Application Services form opens.
        Field Description
        Rule Definition Select a preconfigured CI relationship.
        Alternatively, create a new CI relationship:
        1. Click New.
        2. Select the CI class from the Parent Type list.
        3. Select the relationship type from the Relationship Type list.
        4. Select the CI class from the Child Type list.
        5. Click Submit. The new CI relationship is added to the CI Relationship Type Rule Definitions [cmdb_rel_type_rule_definitions_list] table.
        For example, to discover Linux servers hosting storage devices, select the following values:
        • Parent Type: Linux Server [cmdb_ci_appl_dot_net]
        • Relationship Type: Contains::Contained by
        • Child Type: Storage Device [cmdb_ci_storage_device]
        Is reverse Select this check box if the tagged CI in the relationship is the CI belonging to the child CI class.
        Used By Select Service by Tags.
        Active Select this check box to use this CI relationship in the tag-based discovery.

        Alternatively, clear this check box to exclude this CI relationship from the tag-based discovery.

        Note: By default, you can have only five CI relationships participating in tag-based discovery. To change the maximum number of active CI relationships, edit the value for the svc_by_tags.max.traversal.rules.active property in the System Property [sys_properties] table.
        Order Enter a number for the order. The system uses CI relationships for discovery in sequence from low order to high.
      3. Click Submit in the Traversal Rules for Application Services form.

    What to do next

    If you fine-tune the default configuration after creating application services based on tags, recalculate previously created application services:
    1. Navigate to Service Mapping > Services > Application Services.
    2. Click the relevant application service.

      The application service form opens.

    3. Click Recalculate Service under Related Links.
    4. Repeat these steps for all relevant tag-based services.
    Related concepts
    • CI relationships in the CMDB

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Configure tag-based discovery

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Configure tag-based discovery

      Fine-tune the default configuration to control which CIs Service Mapping includes in application services during tag-based discovery.

      Before you begin

      Learn about the default feature configuration covered in Tag-based discovery in Service Mapping.

      Role required: sm_admin

      About this task

      Control which CIs can become part of application services in the following methods:
      Include CIs based on classes
      Define the CI classes to allow only CIs belonging to these CI classes or their extensions to participate in tag-based discovery. By default, this list is empty and CIs belonging to all CI classes are included in tag-based discovery.
      Exclude CIs based on their install status
      By default, CIs with the Retired or Absent install status are not included in application services, based on tags. You can broaden this list of install statuses to include statuses like Pending install or Stolen, for example.
      Modify CI relationships used for tag-based discovery
      Service Mapping includes CIs that are part of these relationships even if these CIs do not have tags assigned to them. The CI relationships participating in tag-based discovery are stored in the Application Services [svc_traversal_rules] table. You can exclude preconfigured CI relationships from tag-based discovery. You can also configure additional CI 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.
      Note: You cannot delete or modify preconfigured CI relationships used for tag-based discovery from the Application Services [svc_traversal_rules] table.
      Table 1. Preconfigured CI relationships participating in tag-based discovery by default
      CI Relationship CI
      Virtual Machine Instance [cmdb_ci_vm_instance] Virtualized by::Virtualizes Hardware [cmdb_ci_hardware]
      Hardware [cmdb_ci_hardware] Runs::Runs on Application [cmdb_ci_appl]
      Kubernetes Pod [cmdb_ci_kubernetes_pod] Contains::Contained by Operating-system-level Virtualization Container [cmdb_ci_oslv_container]
      Note: Service Mapping user interface refers to CI classes as CI types.

      Procedure

      • To include CIs based on classes, perform these steps:
        1. Navigate to Service Mapping > Administration > Properties.
        2. Enter CI classes separated with a comma in the svc_by_tags.classes.whitelist property field.

          Define CI classes to control which CIs participate in tag-based mapping.
        3. Click Save.
      • To exclude CIs based on their install status, perform these steps:
        1. Navigate to Service Mapping > Administration > Properties.
        2. Enter values for install statuses using a comma to separate these values in the svc_by_tags.install_status.blacklist properties.

          Define install statuses to exclude CIs with these statuses from the tag-based discovery.
        3. Click Save.
      • To exclude preconfigured CI relationships from tag-based discovery, perform the following steps:
        1. Navigate to Service Mapping > Administration > Tag-based Service Traversal Rules.
          The Application Services [svc_traversal_rules] table appears filtered to show only CI relationships used for tag-based discovery. Preconfigured CI relationships, used in tag-based discovery by default, have the true value in the Base System Rule column.

          Table containing information on CI relationships used in tag-based discovery.
        2. Click the preconfigured CI relationship you want to exclude from discovery.
          The Traversal Rules for Application Services form opens.
        3. Clear the Active check box.
        4. Click Submit in the Traversal Rules for Application Services form.
      • To add a CI relationship or edit an existing CI relationship that is not preconfigured, perform the following steps:
        1. Navigate to Service Mapping > Administration > Tag-based Service Traversal Rules.
          The Application Services [svc_traversal_rules] table appears filtered to show only CI relationships used for tag-based discovery. Preconfigured CI relationships used in tag-based discovery by default have the true value in the Base System Rule column.
        2. Click the existing CI relationship you want to modify or click New to use an additional CI relationship in the tag-based discovery process.
          The Traversal Rules for Application Services form opens.
          Field Description
          Rule Definition Select a preconfigured CI relationship.
          Alternatively, create a new CI relationship:
          1. Click New.
          2. Select the CI class from the Parent Type list.
          3. Select the relationship type from the Relationship Type list.
          4. Select the CI class from the Child Type list.
          5. Click Submit. The new CI relationship is added to the CI Relationship Type Rule Definitions [cmdb_rel_type_rule_definitions_list] table.
          For example, to discover Linux servers hosting storage devices, select the following values:
          • Parent Type: Linux Server [cmdb_ci_appl_dot_net]
          • Relationship Type: Contains::Contained by
          • Child Type: Storage Device [cmdb_ci_storage_device]
          Is reverse Select this check box if the tagged CI in the relationship is the CI belonging to the child CI class.
          Used By Select Service by Tags.
          Active Select this check box to use this CI relationship in the tag-based discovery.

          Alternatively, clear this check box to exclude this CI relationship from the tag-based discovery.

          Note: By default, you can have only five CI relationships participating in tag-based discovery. To change the maximum number of active CI relationships, edit the value for the svc_by_tags.max.traversal.rules.active property in the System Property [sys_properties] table.
          Order Enter a number for the order. The system uses CI relationships for discovery in sequence from low order to high.
        3. Click Submit in the Traversal Rules for Application Services form.

      What to do next

      If you fine-tune the default configuration after creating application services based on tags, recalculate previously created application services:
      1. Navigate to Service Mapping > Services > Application Services.
      2. Click the relevant application service.

        The application service form opens.

      3. Click Recalculate Service under Related Links.
      4. Repeat these steps for all relevant tag-based services.
      Related concepts
      • CI relationships in the CMDB

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login