Skip to main content
Version: 5.0

Asset Configuration Settings

warning

All asset configurations created prior to version 5.0 will use the legacy calculation algorithm.

For more details on the update process, see Migrating Asset Configuration.

To ensure proper operation of the updated calculation algorithm, integration with Postgres must be configured. More information is available here.

List of Asset Configurations

The asset configuration page displays a table of existing asset configurations:

List of Asset Configurations

The table can be sorted by columns, filtered via the Search input field, or using filters like Enabled, Disabled, or Tags.

For each asset configuration, the Actions column provides the following options:

  • Tags – view the list of tags
  • Permissions – configure read/write permissions based on user roles
  • Enable/Disable – toggle background data collection by the calculation module
  • Execution Statistics – navigate to the calculation module's execution stats
  • Delete – remove the asset configuration

To edit a configuration, click the Edit button.

You can also import a new configuration or export an existing one using the Import and Export buttons at the top of the table.

Asset Configuration Relationships

To view all asset configuration relationships, go to the Relations tab.

This page displays information about configured relationships between asset configurations:

Asset Configuration Relationships

The page includes a Relations List table and a Relations Map visualization.

warning

Only asset configurations using the updated calculation algorithm can be linked together!

Relations List

The relations list shows all existing links.

It can be filtered using the Search field.

To create a new link, click Add Relation, then select the asset configurations to link and provide the field mapping details:

Create Relation Dialog

Each row in the Actions column includes:

  • Edit – modify the relation settings
  • Delete – remove the relation

Click the row expand icon to view relation field details:

Relation Fields

Relations Map

The relations map visualizes asset configurations as nodes and their relationships as arrows.

To create a relation, drag a point from one side of a node to the opposite point on the target node (e.g., from the right point of one node to the left point of another).

This opens the relation creation window with the selected nodes prefilled:

Create Relation from Map

note

Node layout on the map is random by default. You can rearrange them, then use Save Layout to apply changes or Cancel to revert.

Use the Hide Nodes without Relations toggle to display only related configurations.

Clicking a node shows its asset configuration fields:

Node Field Info

Hovering over a relation arrow reveals which fields are used in the relationship:

Field Info on Map

Configuration Settings Description

Configuration Management

To create or edit a configuration, click Create or use the Edit action in the table. A configuration form will appear.

note

Fields in the General and Schedule sections are mandatory.

A configuration includes the following sections:

  • General Settings – general information about the asset

  • Fields – basic and additional fields used in the asset's structure

  • Sources – list of data sources and field-mapping rules

  • Linking – key fields used to link sources

  • Prioritization – rules defining field extraction priority from sources

note

General and Schedule fields in General Settings are mandatory.

By default, the updated calculation algorithm is used.

To switch to the legacy algorithm, turn off the Use new algorithm toggle.

General Settings

This tab includes:

  • General – name of the configuration and storage name

  • Schedule – interval or cron expression for running background collection

    note

    Supported types: Interval or Cron Expression

  • Asset Settings – asset name and time-to-live settings

  • Display Settings – visual representation (icon and color)

  • Execution Parameters – backend options like batching, indexing, replication, etc.

note

The Asset Name field supports tokens based on basic and additional fields, e.g., $hostname$ - $os$.

The Time-to-live must be a single-unit value like 20h, 2d, 30s.

warning

Display Settings and Enable Data Replication to Index are only available for configurations using the updated algorithm.

Batch Changes, Use Index, Join with Empty, and Fast Search Only are only available with the legacy algorithm!

warning

If replication to index is enabled, the asset database built by the background task will be copied to the index in the legacy structure.

If the index does not exist, it will be created automatically.

Fields

The Fields tab allows configuring asset fields with the following attributes:

  • Basic Field – defines if the field is basic or additional

  • Field Name – technical name used in calculations (must be unique)

  • Display Name – optional name shown in the UI

  • Coefficient

    note

    The coefficient affects similarity calculations between assets during matching. Similarity is determined by k = c / (a + b - c)

    • c: matching basic fields
    • a: basic fields in existing asset
    • b: basic fields in new asset Assets are considered similar if: k ≥ 0.5 when b ≤ 5 k ≥ 0.554 when b > 5 The coefficient multiplies the presence of a field in a, b, and c. A value of 0 excludes it; 1 includes it once; n includes it n times.
note

Use the Add Field button to add a new field.

Sources

Click Add Source, then expand the menu to configure:

  • Source Name in Assets

  • Index – storage index

  • Time Interval – data collection timeframe

    note

    The time filter uses intervals like 90d, 24h, 15m. Default field is @timestamp. Units: m, h, d, w, M, y. If interval uses minutes, the end is now; otherwise, it's the start of the previous hour. OpenSearch format documentation.

  • Auto-detect Aggregated Fields – toggle for using aggregatable fields

  • Field Mapping Rules – map source fields to configuration fields

note

Use Add Field to map new fields.

Linking

Click Add to configure key fields:

  • Sources to Link – choose from configured sources

  • Linking Fields – choose from basic or additional fields

Prioritization

Click Add Priority, then expand the menu:

  • Field – field to prioritize

  • Extraction Order – define priority across sources

Use Add Source to define extraction order.

note

The Priority Level sets extraction order; lower values come first. Equal priorities result in an array value in the asset.

Configuration Setup Process

To access configuration list, select Assets in the Inventory menu:

Configuration List

To configure, click Create or Edit, opening the configuration form:

Edit Configuration

Complete the General Settings tab, then define fields in the Fields tab:

Field Configuration

In Sources, add and configure data sources:

Source Configuration

In Linking, define field relationships:

Linking Configuration

Then configure Prioritization:

Prioritization Configuration

Once all settings are complete, click Save. You’ll be redirected to the configuration list with a confirmation.

Asset Configuration Migration

note

This section applies only to configurations using the legacy algorithm.

warning

Once migration is complete, reverting is not possible!

When opening a configuration with the legacy algorithm, you’ll see a banner for available migration:

Migration Available

Click the banner and Start Migration to begin:

Start Migration


Once started, the banner will indicate migration is in progress:

Migration in Progress

warning

Migration occurs in the background (you may leave the page).

Assets are migrated in batches of 10,000 records.

Some configuration-related features may be unavailable during migration.

Progress updates are shown via the banner. You can cancel or view details:

Migration Progress View


Once complete, a success message will appear:

Migration Complete

Click to view migration results:

Migration Complete Detailed

note

To dismiss the success notification, click Close.

If an error occurs, you’ll see a corresponding alert:

Migration Error

Click the alert to see error details and restart migration if needed:

Migration Error Detailed

warning

If migration fails or is manually canceled, all transferred data will be deleted!