Axonius to CMDB Field Mapping
  • 1 Minute To Read
  • Print
  • Share
  • Dark
    Light

Axonius to CMDB Field Mapping

  • Print
  • Share
  • Dark
    Light

The create and update CMDB enforcement actions let you also configure and control the fields values of each created/updated asset in the CMDB based on Axonius fields.

As part of the enforcement action configuration, the Axonius to [CMDB solution name] field mapping field (e.g. Axonius to ServiceNow field mapping) lets you define map Axonius fields to the CMDB fields. The input should be key/value pairs in a JSON format.
For example: {"axonius_field1":"servicenow_field1", "axonius_field2":"servicenow_field2"}

Axonius Fields

  • Axonius field names can be supplied in a short name or in a full name format. The following table provides examples for each format for each field type:
Field Level Field Type Field Label in GUI Format - Short Name Format - Full Name Comment
Aggregated Simple image.png hostname specific_data.data.hostname
Adapter Simple image.png aws_adapter:hostname adapters_data.aws_adapter.hostname
Aggregated Complex image.png installed_software:name specific_data.data.
installed_software.name
Mapping is supported only for the 1st level fields in a complex field hierarchy
Adapter Complex image.png tanium_asset_adapter:
installed_software.name
adapters_data.tanium_asset_adapter.
installed_software.name
Mapping is supported only for the 1st level fields in a complex field hierarchy
  • A field that contains multiple values will be mapped to a single string consists of the various values separated by comma.
  • The supplied field mapping can override any of the default mappings done when the CMDB entity is created/updated.
  • If the supplied Axonius field is not found, the specific key/value pair will be ignored.

CMDB Fields

  • CMDB field name should be the CMDB technical name as defined in the CMDB API.
Was This Article Helpful?