Skip to main content

Collect and review system data

System collection guide

Collect current data into the Vault, validate the result, and use collection history when you need to investigate or restore a prior snapshot.

Collection reads the selected tables from a connected system and loads the result into the Vault. Collect after changing a system connection or data model, and before processes need current identity data.

Collect before building on the dataFilters, mappings, roles, and relation validation depend on the data currently loaded in the Vault. Run and review a collection before relying on a new or changed configuration.

Collect and validate current dataDirect link to Collect and validate current data

Collect and validate current system data

Collect a systemDirect link to Collect a system

  1. Open Systems > Overview.
  2. Select Collect for the system.
  3. Watch the system status while NIM collects the selected tables.
  4. When the status changes to success, review the returned messages in the Log pane.

Outcome: the collected tables are loaded into the Vault and ready for review.

Step 1 of 3

Work with collection historyDirect link to Work with collection history

Every collection creates a timestamped snapshot. Use the history to compare a past result, temporarily load a known collection into the Vault, or remove a snapshot that is no longer needed.

Review and manage collection history

View past system collectionsDirect link to View past system collections

  1. Open Systems > Overview.
  2. Select View System Collection History for the system.
  3. Select a past collection, then choose View Collection Log to review its result.

To inspect data from a specific historical table collection, open that table, select Collection History, and choose View Collection History.

View past table collectionsDirect link to View past table collections

The selected historical table data appears in the Table Data pane. Use it to compare a prior snapshot with the data currently loaded in the Vault.

Step 1 of 3

Identify the loaded and anonymized collectDirect link to Identify the loaded and anonymized collect

Data views show the loaded collect rather than the newest collect on disk. The grid title names it and indicates when a newer collect is not loaded. Collection history includes an Anonymized column so you can distinguish processed test data from original collects.

Before loading a historical collect, review both its identity and anonymization state. Loading anonymized data also blocks system functions and restricts mail; see Anonymize collected data. Loading a different collect changes what filters and downstream processes see.

Next stepsDirect link to Next steps

  • Review Dataset statistics when you need deeper collection validation metrics.
  • Configure collection guards to stop unexpected source changes before they affect downstream work.
  • Use filters to select and shape the current Vault data for your processes.