DC-UI Kickstart Guide

1. Navigate to Inventories page – Click "Inventories" in the main nav (or go to /dc-ui).
2. Understand the system list columns:
   • System Name – Identifier for the data source
   • System Type – Template (e.g., LDAP, SCIM)
   • Inventory Status – Running, Not Running, or Stopping
   • Health mini-graph – 24-hour timeline of success/failure bars
   • Entities – Count with eye icon linking to Entity Explorer
3. Click on the Health mini-graph – Opens a view of admin events for that system (filtered to category=health_check).

What are entities?

Entities are the collected data objects from your systems—users, groups, accounts, etc. Each entity has transformed_data (the mapped fields) and metadata (keys, timestamps, hash).

1. Navigate to Entities Explorer – Click "Entities" in the nav.
2. Select a system from the dropdown.
3. Choose entity type – e.g., users, groups, accounts.
4. Filter by date ranges – Updated On, Last Confirmed, Created, Store Updated (four independent ranges).
5. Click the eye icon on a row to view full entity details (transformed_data JSON, keys, timestamps).

What is an inventory?

An inventory is a run that connects to a system, collects entities, and optionally persists or publishes changes. Each inventory belongs to a stream — a multi-stream system can have its streams running concurrently. You can trigger inventories manually from DC-UI.

Five Trigger Modes

DC has five engine-level trigger modes. The Trigger Type modal in DC-UI surfaces them as four cards — Replay and Readonly Replay share one card with a Mode Switch. Day 27 covers the modal mechanics in detail.

1. On Inventories page, find a system and click the trigger button.
2. Select Detached Readonly mode.
3. Choose inventory_input – Empty or from previous run.
4. Trigger and watch real-time status updates.
5. View results after completion (steps, connector calls, changes).

What are admin events?

Admin events are an audit trail of operations: health checks (automatic and manual), inventory triggers, configuration changes, system enable/disable, and DC lifecycle events.

1. Navigate to Admin Events page – Click "Admin Events" in the nav.
2. Filter by category – Health checks, triggers, config changes.
3. Filter by system – Narrow to a specific system.
4. Click an event to view full details (timing, errors, YAML diffs for config changes).

In this kickstart we only view configuration—editing is covered in Week 5.

1. Navigate to Config > Systems – Opens the systems configuration list.
2. View system details – Click a system to see its configuration (connection, destinations, etc.).
3. See credential pointer – Each system references credentials via a pointer (e.g., openbao+kv2://secret/datacollector/system-name).
4. Check diff destinations – Where changes are published. The three destination types are EmpowerID (API sync), Kafka (streaming), and File (local YAML, mainly for debugging).
5. Per-stream next_inventory_input – Each stream has its own NII (the JSON state passed forward to its next inventory). You'll edit it routinely; for now, just notice it exists per stream, not per system.