Advanced Settings
Advanced settings can either apply to all connections for this adapter or to a specific connection. Refer to Advanced Configuration for Adapters.
You can use Advanced Configuration settings to fine-tune how the ServiceNow adapter fetches data. These settings can be applied globally to all adapter connections, or customized for individual connections.
Per-connection customization is useful when you need multiple fetch cycles for the same data source, for example:
- A light, frequent fetch for quick updates.
- A less frequent, more resource-intensive fetch for deeper data collection.
Accessing Advanced Configuration
- Navigate to the Adapters page → search for
ServiceNow→ click on the adapter tile. - On the left menu, select Advanced Configuration under Advanced Settings.
Advanced Configuration Parameters
At the top of the Advanced Configuration, you can choose asset types that are relevant to specific advanced configurations.
- From the dropdown, select one or more asset types.
- The relevant advanced configurations are displayed.
- Next to certain configurations, you can find a small info icon. Hover over the icon to see more information.
- The Advanced Configuration page is divided into sections, which can be collapsed to make it easier to navigate.
Settings field descriptions
Fetch Settings
-
Fetch Assets - Select this option to allow Axonius to fetch devices from ServiceNow.
-
Assets tables to fetch - By default, Axonius fetches all tables of assets. To filter out tables of assets from the fetch, deselect one or more of the options in the table.
-
Assets sub-tables to fetch - By default, Axonius fetches all sub-tables of assets. To filter out sub-tables of assets from the fetch, deselect one or more of the options in the table.
-
Table schema mapping - This option helps you parse assets into categories by creating an array, where each row contains the fields listed below. Currently, the asset types supported for custom parsing are: Devices, Compute Services, Compute Images, Containers, Object Storage, Databases, Load Balancers.
Click + Add Table to create a new array (you can create multiple tables) or x to delete a table.- Asset type - From the dropdown, select a supported asset type.
- Table name - Type a string representing the name of the table, for example:
u_cmdb_ci_computer - Query (optional) - Enter a list of strings to be used as the
sysparm_filterAPI parameter. See the ServiceNow documentation on Query Parameters for more information. - Fields to fetch (optional) - Enter fields to fetch from the corresponding table. If you leave this field empty, all fields will be fetched by default.
-
Fetch users - Select this option to fetch all users in the system.
-
Fetch roles for users - Select this option to fetch the roles used by each user.
-
Use existing user data during device fetching - Select this option to add various user fields to the devices (for example: Owner, Assigned To, etc.) based on the associated Users Assets fields. The Fetch users data option will be ignored.
-
Fetch only parsed fields for users - Enabled to fetch only parsed fields from ServiceNow.
- If disabled (default setting), fetches all fields from ServiceNow, shows them all in “view advanced” section and parses only the fields required.
-
Custom User Schema - Use these settings to add a JSON file to fetch information from one object to another. Refer to Custom User Schema
-
Additional user table names - Enter one or more ServiceNow table names separated by commas from which Axonius will fetch entries and parse them into users. Table names should be of the format
cmdb_ci_my_linux_server.- You can use this setting in 2 ways:
- A list of tables to fetch in addition to the built-in tables. In this case the format should be table_name(, table_name). When the table names are separated by commas.
- A list of tables with filters. In this case the format should be (table_name(:sysparm_query)(;table_na…)), where sysparm_query is a ServiceNow query with ServiceNow operators as defined in Operators available for filters and queries and each table name together with a query (filter) is separated by a semicolon. (Fields in brackets are optional parameters)
- When supplied, the adapter will fetch data from all of the additional tables listed, make them into users, then proceed with fetching the default hardcoded subset of tables Axonius usually fetches from. The tables listed in this field take precedence over the default ServiceNow tables queried by Axonius, a Ci fetched from these tables will now be totally ignored as redundant in the later “default” fetching process.
The settings here for filters on the table names listed in this field apply exclusively to the list of tables in this field. Other advanced settings that you make do not serve as filters to the table names listed in this field.
For example: if Additional device table names==
cmdb_ci_ip_switch:install_statusIN1;cmdb_ci_ip_router:install_statusIN1;and Install status number exclude list==2,3,4, then all of the ServiceNow built in device tables will be fetched with excluded of install_status of 2,3,4 and the specific tables in Additional device table names will be an “inclusion” of install_status of 1. - You can use this setting in 2 ways:
-
Fetch users data for devices (default: Enabled) - Select this option to fetch user data and add relevant user fields to the devices (for example: Owner, Assigned To, etc.).
- The Users table in ServiceNow is a large table. Therefore, if you are running Axonius on-premises, fetching this data requires more time, RAM, and CPU from the adapter's connections.
-
Fetch last user transaction from syslog_transaction table - Select this option to fetch and parse the latest transaction (from syslog_transaction table) for each ServiceNow user, to the field “Last Transaction”.
-
Fetch VPN devices from 'cmdb_ci_vpn' table (default: Enabled) - Select this option to fetch VPN devices from 'cmdb_ci_vpn' table.
-
Fetch only cmdb ci computer table - Select this option to fetch only devices from the cmdb_ci_computer table. The adapter will not fetch any other device tables.
-
Do not fetch devices without IP address, MAC address and serial number - Select this option to only collect information of devices if they have an IP address, MAC address, and serial number.
-
Exclude VMs tables - Select this option to not collect device assets from tables in ServiceNow that are related to Virtual Machines.
-
Install status exclude list (optional) - Specify a comma-separated list one or more install statuses to exclude from the fetched data. If supplied, this adapter will not fetch devices from ServiceNow if their install status is in the specified list. This field only accepts integers (such as 7, and not strings).
-
Install status include list (optional) - Specify a comma-separated list of one or more install statuses to include in the fetched data. If supplied, this adapter will only fetch devices from ServiceNow if their install status is in the specified list. This field only accepts integers (such as 7, and not strings).
- The values supplied in this field are applicable only if Install status exclude list is empty.
-
Operational status exclude list (optional) - Specify a comma-separated list of one or more operational statuses to exclude from the fetched data. If supplied, this adapter will not fetch devices from ServiceNow if their operational status is in the specified list.
-
Operational status include list (optional) - Specify a comma-separated list of one or more operational statuses to include in the fetched data. If supplied, this adapter will only fetch devices from ServiceNow if their operational status is in the specified list.
- The values supplied in this field are applicable only if Operational status exclude list is empty.
In order for the above Install Status and Operational Status Include/exclude fields to work correctly, the Axonius ServiceNow user account must have access to the sys_choice table.
For the Install Status and Operational Status include/exclude fields to function correctly, the adapter must have read access to the
sys_choicetable. -
Populate device upstream and downstream fields - Select this option to populate the fields “upstream“ and “downstream“ for devices.
-
Upstream / downstream fields: display as flat list - Select to display the Upstream and Downstream field values for Devices as a flat list rather than a graph. The Relation Depth displayed in this format is greater - up to 10.
-
Fetch upstream related Application Services information - Select this option to parse information from the Application Services table (cmdb_ci_service_discovered) of any application service existing in a device upstream relations.
-
Fetch upstream related Application Services extended information - Select whether to fetch information from the cmdb_ci_service_auto table and additional fields from the cmdb_ci_service_discovered table not fetched by the Fetch upstream related Application Services information parameter.
-
Fetch upstream related FCI details from 'u_applications' - Select this option to fetch information from u_applications table and enrich devices with it.
-
Fetch upstream related Certificate information from 'cmdb_ci_certificate' - Select this option to fetch the certificate information of device assets from ServiceNow.
-
Fetch upstream related Business Application - Select whether to fetch the Business Application information of device assets from ServiceNow.
-
Fetch upstream related Application from 'cmdb_ci_appl' table - Select to fetch information from the 'cmdb_ci_appl' table about applications related to a device.
-
Fetch active compliance policy exceptions from 'sn_compliance_policy_exception' Select this option to link 'active' compliance policy exceptions as identified by ServiceNow Governance, Risk and Compliance (GRC) to the respective devices.
-
Fetch model information from 'cmdb_model' (default: Enabled) - Enable this setting If the 'model_id' field value is a reference to the cmdb_model table.
- If enabled, this adapter will use the reference in the 'model_id' field to fetch the device_model and device_manufacturer from the cmdb_model table.
- If disabled, this adapter will fetch only the value of the 'model_id'.
-
Fetch active model lifecycle information from 'cmdb_hardware_model_lifecycle' - Select this option to fetch active model lifecycle information from the cmdb_hardware_model_lifecycle table and parse it as a list object named “Model Lifecycle”.
-
Fetch NIC information from 'cmdb_ci_network_adapter' table (default: Enabled) - If enabled, this adapter will fetch network interface information from the cmdb_ci_network_adapter table and from the matching cmdb_ci_ip_address table.
-
Fetch only discovered NICs with IP information from 'cmdb_ci_network_adapter' table - Select whether to fetch network interface information from the cmdb_ci_network_adapter table that has an IP address.
-
Fetch Platform Offering from ‘service_offering' table - Select to fetch information from the ‘service_offering’ table and enrich the device with the service offer name if a direct reference exists between the device and the table. Check the Fetch device relations field to search for a relation between the service offering and the device and create a new structure for the device called “CMDB Service Offering” with the details of the service offering.
-
Fetch Software package information from 'cmdb_sam_sw_install'/'cmdb_software_instance' table - Select this option to fetch software package information from the ''cmdb_sam_sw_install'/'cmdb_software_instance' table.
-
Fetch CI key-values(tags) information from cmdb_key_value table - Select this option to fetch the table cmdb_key_value and enrich each device that has matching key-value records in the cmdb_key_value table.
-
Fetch running processes information from cmdb_running_process table - Select this option to fetch running processes information.
-
Fetch ALM information from alm_asset table (default: true) - By default Axonius fetches additional data for existing devices from alm_asset table. Clear this option if you do not want to fetch ALM information.
-
Fetch Device contract information from 'ast_contract' for the following parent contract numbers - Specify a comma-separated list of parent contract numbers. This option requires the 'Contract Management' plugin.
- If supplied, this adapter will fetch contract information (number, short description) for the specified list, and will add the contract information to the devices associated with the contract (Contracts complex field), based on the relationship defined in ServiceNow.
- If not supplied, this adapter will not fetch contract information.
-
Fetch Device divestiture contract information from 'ast_contract' for the following parent contract numbers - Specify a comma-separated list of parent contract numbers. This option requires the 'Contract Management' plugin.
- If supplied, this adapter will fetch divestiture contract information (number, short description) for the specified list, and will add the divestiture contract information to the devices associated with the contract (Divestiture Contracts complex field), based on the relationship defined in ServiceNow.
- If not supplied, for this adapter will not fetch divestiture contract information.
-
ServiceNow Fields are true - Enter one or more parameters, separated by commas, and filter only devices where these parameters are true. If the device does not have the field, the device is fetched.
-
Fetch PC attributtes - Fetch device PC Attributes from the 'u_pc_attributes' table, where
u_type=Attributes -
Fetch CI Exceptions - Select this option to fetch records from the u_configuration_item_exception table and enrich the device with related exception information such as exception name, reason, related software etc.
-
Fetch Portfolio fields from u_ip_portfolio_mapping table - Select this option to fetch Portfolio fields in the u_ip_portfolio_mapping table.
-
Fetch common cost center details - Select this option to fetch information from the cmn_cost_center table.
-
Fetch Table Hierarchy - Select this option to create the table hierarchy of a device.
-
Enrich CMDB CI Associations - Select this option to enrich each device with the services that the devices are associated with.
-
Fetch Databases As Assets - Enter a (comma-separated) list of tables. Axonius fetches the records from those table and parses them as database entities.
-
Fetch Business Application as Asset - Toggle on to fetch Business Application as an asset.
- Business Application tables list - Enter a list of tables to fetch Business Application from (default is 'cmdb_ci_business_app').
-
Do not fetch devices or users marked as excluded - Select this option to fetch assets that have the u_exclude_from_discovery field set as True in ServiceNow.
- If disabled, this adapter will fetch all assets from ServiceNow.
As a prerequisite, u_exclude_from_discovery field must be created and defined in ServiceNow as a Boolean field.
-
Include assets if they have the following field with the following value(s) - Enter one or more ServiceNow tables with a specified value, in the format (table_name:)field_name:(filtered_value,filtered_value). Separate entries with semi-colons. The table name must be exactly one of the values listed here:
cmdb_ci_computer,cmdb_ci_vm,cmdb_ci_vm_instance,cmdb_ci_printer,cmdb_ci_netgear,u_cmdb_ci_computer_atm,cmdb_ci_comm,cmdb_ci_cluster,cmdb_ci_cluster_vip,cmdb_ci_facility_hardware,cmdb_ci_msd,u_cmdb_ci_dinar_infrastructure_object,cmdb_ci_vpn. (Fields in brackets are optional parameters)- If a field is supplied, this adapter will fetch devices which have a ServiceNow table that contains a field with the value defined.
The filters here overwrite any other filters you set for tables. If you choose this setting, you cannot choose other predefined ServiceNow advanced settings table filters as well.
- If a field is supplied, this adapter will fetch devices which have a ServiceNow table that contains a field with the value defined.
-
Exclude assets if they have the following field with the following value(s) - Enter one or more ServiceNow tables with a specified value, in the format (table_name:)field_name:(filtered_value,filtered_value). Separate entries with semi-colons. The following table names are supported:
cmdb_ci_computer,cmdb_ci_vm,cmdb_ci_vm_instance,cmdb_ci_printer,cmdb_ci_netgear,u_cmdb_ci_computer_atm,cmdb_ci_comm,cmdb_ci_cluster,cmdb_ci_cluster_vip,cmdb_ci_facility_hardware,cmdb_ci_msd,u_cmdb_ci_dinar_infrastructure_object,cmdb_ci_vpn. (Fields in brackets are optional parameters)-
If a field is supplied, this adapter will exclude devices from the adapter fetch which have a ServiceNow table that contains a field with the value defined.
The filters here overwrite any other filters you set for tables. If you choose this setting, you cannot choose other predefined ServiceNow advanced settings table filters as well.
-
-
Fetch properties settings - Select this option to fetch general ServiceNow settings.
To fetch settings using this advanced configuration, ensure that there are no ACL configurations blocking the records from the sys_properties table in ServiceNow.
-
Fetch password policy settings - Select this option to fetch password policy related settings.
-
Fetch groups - Select this option to fetch ServiceNow groups as assets.
-
Fetch roles - Select this option to fetch ServiceNow roles as assets.
-
Fetch users' group membership - Select this option to fetch ServiceNow users group membership.
-
Fetch active extensions from 'v_plugins' - Select this option to fetch active extensions.
-
Fetch entities from 'cmdb_ci_ip_network' as Networks assets - Select this option to fetch entities from 'cmdb_ci_ip_network' as Networks assets.
-
Fetch Activities From X days Ago - Enter the number of days to retrieve recent activities information.
-
Ignore SaaS Applications Repository and parse all applications - Select this option to fetch all applications even if they are not in the Axonius SaaS Applications Repository.
-
Custom Assets schema for Devices, Business Applications, Databases - Use these settings to add a JSON file to fetch information from one object to another. Refer to Custom User Schema
-
Fetch Assets Relations -
-
Fetch dynamic dropdown values - When selected, field values for the dynamic dropdown lists in the related Enforcement Actions are fetched and populated into the lists.
-
Fetch from the following Read Replica category (Must be supported on instance) - Fetch from the specified Read Replica.
Parsing Settings
- Save only active users - Select this option to save only users with active field set to
true. - Users Email include list - Enter a comma-separated list of email strings. Only users whose email addresses contain any of these strings will be fetched. The strings don’t need to be full email addresses, partial matches are allowed because the filter uses a Contains search.
- Resolve Username based only on name field - Select this option so that the Username field in Axonius will display the value of the name field in the ServiceNow record.
- JSON fields to show in basic view - You can configure fields that generally appear in JSON to appear in Basic view. Refer to Showing JSON Fields in Basic View
- Parse IP addresses from device raw "ip_address" field - Select this option to parse IP addresses from the device raw "ip_address" field.
- Exclude disposed and decommissioned devices - Select this option to not collect information on devices if their status in ServiceNow is 'Disposed' or 'Decommissioned'.
- Ignore retired devices that have not been seen by the source in the last X hours (default: 0) - Enter 1 or more hours to ignore retired devices that have not been seen by the source. A value of 0 means to fetch all devices.
- Use 'cmdb_ci' table instead of 'alm_asset' table for install status and location - Select this option to collect the location and Install Status directly from the record instead of from the 'alm_asset' table.
- Save only virtual devices - Select this option to save only devices with virtual or u_is_virtual fields set to
true. - Parse operational status - Select this option to parse the operational status from the 'operational_status' field.
- Populate device and applications upstream and downstream fields - Select this option to populate the device and applications upstream and downstream fields, which are used for the asset graph.
- Populate the Device Company field with z_support_group_manager_company - Select this field to populate the Device Company field in the adapter basic view with the “z_support_group_manager_company” data.
- Populate the Device Company field with z_assigned_to_company - Select this field to populate the Device Company field in the adapter basic view with the “z_sassigned_to_company” data.
- Populate the Device Owner based on assigned_to parsed field - Select this option to populate the Axonius owner aggregated field based on the ServiceNow "assigned to" field instead of the "opened by" field.
- When company does not exist, use owner as Company - If the "company" field value in a device doesn't exist, it will use the device owner as the company value
- Use dns_domain device raw field as hostname - Select this option to to take the hostname value from the dns_domain ServiceNow field value (instead of from the name).
- Use asset_tag raw device field as hostname fallback - if no hostname exist - Select this option to take the hostname value from the asset_tag ServiceNow field value (instead of from the name).
- Use "asset" raw device field as Asset Name - Use the value of the device's "asset" raw field as the value for Asset Name. This setting applies only to devices.
- When hostname does not exist, use asset name as hostname - Select this option to set the asset name as the hostname for the device in ServiceNow if a hostname does not exist.
- Remove domain suffix from hostname field - Select this option to remove the domain suffix from the ServiceNow Hostname field.
- RAM from source in GB - Select this option to display the RAM data fetched from ServiceNow in GB memory units instead of MB memory units.
- Parse only IPv4 for devices (exclude IPv6) - Select whether to only parse IP addresses in IPv4 format for devices. By default Axonius parses IP addresses both in IPv4 format and IPv6 format.
- Extract software version and name from Software Name - Select this option to extract the correct software name and version when the field fetched by ServiceNow does not contain this correctly.
- Use 'last_discovered' device field exclusively as 'last_seen' - Select this option to compute the 'last_seen' field from the 'last_discovered' raw field, if this field does not exist 'last_seen' will not exist.
- When disabled, this adapter will use
max('last_discovered', ‘sys_updated_on’)to compute last_seen.
- When disabled, this adapter will use
- Use sys_id as device ID (Might cause device duplication) - Select this option to only use the devices' sys_id field for the adapter device ID (recommended if the device name might change). If you enable this after the first fetch has already been done, it might cause duplicate devices.
- Use ServiceNow Domain in Asset ID (Might cause device duplication) - Select this option to only use the ServiceNow Domain in the Asset ID. If you enable this after the first fetch has already been done, it might cause duplicate devices.
- Do not use 'Last Seen' for the following tables -
- Enter one or more ServiceNow table names separated by commas that will not be filtered by 'Last Seen'. This adapter will fetch all of the data from the specified tables from all dates.
- To avoid calculating 'Last Seen' for all devices, enter
*in the field.
- Always populate serial number - When selected, Device Manufacturer Serial is parsed even if it contains exclusion keywords, such as "VMware Virtual Platform".
- Exclude Devices OS list - Specify an Operating System name to not fetch devices which run this Operating System.
- Append device model to OS string if the following strings are in the model field - Models containing one of the strings entered in this field (separated by commas) are appended to the OS string.
- Do not add serial number metadata (optional) - Select this option so that metadata such as "VMWare-", "VMWare Inc.", "VMWare Virtual Platform" and any other device model data will not be added to ServiceNow serial numbers.
- Use "VM Object ID" as "AWS Cloud ID" - Use this setting to use the VM Object ID to identify AWS Cloud IDs. When you select this option, if the value of the
object_idconfirms to the following rules:- getting
vm_object_idfromobject_id, - if
vm_object_idstarts from ‘i-’ and length > 10
Then Axonius uses the value of theobject_idin thedevice.cloud_idfield.
- getting
- Devices: Unset Downstream and Upstream fields if not populated in fetch results (optional, default: disabled) - Select this option to automatically clear existing field values in the Downstream and Upstream complex object fields on devices when no new values are returned during a ServiceNow fetch. This is useful for optimizing 'delta fetches' (double fetching).
- Enter additional date fields to consider as 'last seen' - Enter values (comma separated) from fields to calculate the 'Device last seen field'.
- Specify Class Names (Tables) to parse as Network Device assets - Enter device class names to locate for fetching devices as Network Device assets.
- JSON fields to show in basic view (Devices, Business Applications, Databases) - You can configure fields that generally appear in JSON to appear in Basic view. Refer to Showing JSON Fields in Basic View
- Custom Raw fields mapping - Enter a JSON file to duplicate raw fields to different raw fields. This will enable the adapter to treat the asset like a classic ServiceNow asset (rather than a proprietary one).
Advanced Configuration
-
Fetch "cmdb_software_product_model" table for Various Software enrichment - Select this option to fetch and process data from the
cmdb_software_product_modeltable in ServiceNow. This is only supported in adapters that enable Device Software Enrichment. Currently, only FlexNet Manager Suite Cloud enables this enrichment type.You can enrich the Axonius Software table with ServiceNow CMDB data from the CMDB table. For more information, see Enriching Software Assets with ServiceNow CMDB Data.
-
Use the following field when filtering last updated (optional) - Enter a ServiceNow field name to be used as the field that Axonius filters by for the following configurations Fetch devices updated in ServiceNow in the last X hours and
Fetch users updated in ServiceNow in the last X hours- If a field is set, this adapter will fetch devices or users which have the set field that was updated in the time defined.
- When not supplied, this adapter will fetch devices or users which were last updated according to the ‘sys_updated_on’ ServiceNow field.
-
Entries fetched per page (required, default: 500) - Specify the maximum number of entries for this adapter to fetch per page when connecting to the ServiceNow server.
- The supplied value lets you control the performance of all the connections for this adapter. To reduce the number of requests sent to ServiceNow, but to avoid impact on overall performance, you can reduce the Number of requests to perform in parallel value and increase the Entries fetched per page value.
-
Date Format - Generally, ServiceNow automatically identifies the date format. In some cases, the identification is ambiguous. You can set a specific date format for timestamps in ServiceNow. From the dropdown, select either: Automatically Identify, DD/MM/YYYY or MM/DD/YYYY. The default is Automatically Identify.
-
Custom Parsing - Select this option to define how to parse specific fields from the raw data fetched. See Adapter Custom Parsing for more information.
-
Number of requests to perform in parallel (default: 50) - Enter the number of requests to perform in parallel.
-
Enable real-time asset updates (Supported events: New users, New Tickets) - Select this option to update assets in real-time with New Users and New Tickets events.
-
Fetch EC Action ticket updates (optional, default: enabled) - Select this option to configure the adapter to fetch updates on tickets created by Axonius users. The updated ticket information is displayed in the Tickets table showing information on all tickets in the system (Assets> Tickets) or on Tickets of a specific asset (in the Asset Profile of the relevant asset).
Updated 1 day ago
