Configuring sources

By default, the source data in Asset comes from Tanium, populated from saved questions that are scheduled on a frequent basis. You can also configure a database as an asset source.

Configure Tanium source

The Tanium Asset source is configured by default, and you cannot delete the Tanium Asset source.

  1. From the Asset menu, go to Inventory Management > Sources.
  2. For the Tanium source, click Edit .
  3. Add the user name and password for the service account. The selected user must be a Tanium Administrator. You can also disable and change the log level settings for the Asset import process.
  4. Configure the asset data import schedule. The data import schedule determines how often asset data is imported from the Tanium live data into the asset database. This database provides data for offline assets. You can create a standard interval or a Cron schedule. For example, you might create one of the following intervals based on your environment size:
    • Less than 50,000 devices: every 1-2 hours
    • Less than 250,000 devices: every 4 hours
    • Greater than 500,000 devices: consult your TAM to configure the import schedule

    For more information about the Cron syntax, see Reference: Cron syntax.

What to do next

Add attributes from Tanium sensors into Asset. See Configuring attributes.

Configure database source

Enrich Asset inventory data with information from an external database. For example, you might have a database that has information about computers that you want to bring into Asset. To import this data, map columns from your SQL database to the Asset database.

If you use column types (like nchar) that pad values with spaces, your identity mappings on the database source might not work correctly. For example, a computer name like win1 might come through as win1       (with six spaces after it). These values do not match a value win1 in Asset.

  1. From the Asset menu, go to Inventory Management > Sources > New Source.
  2. Configure source settings. Enter a name for the data source, and the server name and credentials. Click Get Schemas. Asset connects to the database and gets the database and schema information. Choose database and schema.
  3. Configure source mappings. Source mappings uniquely identify the assets in your source data, and define how the columns in your source table relate to the Asset database. For an attribute to be available as a reference for mapping, it must only return a single row of value. You can add multiple source mappings from your database source. All the mappings must match for the data to be imported into the Asset database.
    1. Click Add Source Mappings. Choose a source table.
    2. Create identification rules. The columns associated with the selected source table are loaded into the Source Columns field.
    3. Choose a destination attribute. Choose a column in the Asset database. You can create multiple identification rules as necessary.
    4. If you want to remove a source mapping, click Delete . To remove an identification rule, click Remove .
  4. Configure the import schedule. The schedule determines how often asset data is imported from the external database into the asset database. You can create a standard interval or a Cron schedule.

    For more information about the Cron syntax, see Reference: Cron syntax.

  5. Click Create.

If you want to modify the source, go to Inventory Management > Sources. Click Edit . You must enter the credentials for your SQL server again before you can modify the source mappings.

What to do next

Add the attributes from your import table into Asset. See Configuring attributes.

When the data import runs, each row of your import table is evaluated data that is already in Asset. For example, if you created a mapping for your computer ID in the import table, that ID gets matched to the computer ID column in Asset. If a match is found, the attributes that you configured to get imported from your source table are inserted into Asset. If you map an import column that has duplicate values in the table, only the last value is stored in Asset after the load has completed.

Last updated: 7/10/2019 4:51 PM | Feedback