Discovery Mode

Discovery Mode lets you start monitoring without any upfront CMDB setup. Connect a data source and the system learns what’s reporting.

How it Works

1. Create Pulse with Discovery Mode ON
   └── Choose learning duration: 1h, 4h, 12h, 24h, 48h, 7d

2. Learning Phase (e.g., 24h)
   └── Worker collects data from source
   └── Auto-creates entities from discovered hostnames
   └── Scheduler observes but does NOT alert

3. Learning Complete
   └── Asset Group frozen with discovered entities
   └── Monitoring transitions to Active
   └── Alerts generated when assets go silent

When to Use Discovery Mode

• First setup — you don’t know exactly which assets report to a source
• New data source — adding a Kafka topic and want to see what’s there
• Validation — verify that expected assets are actually reporting

When to Use Manual Mode

• Compliance — you need to monitor a specific set of servers from your CMDB
• Known scope — you know exactly which 50 servers should report
• Gap detection — you want to catch assets that have NEVER reported (discovery can’t detect what was never there)

Learning Duration

Duration	Use Case
1 hour	Quick test, development
4 hours	Short-lived batch jobs
12 hours	Covers business hours
24 hours (default)	Full daily cycle
48 hours	Weekend coverage
7 days	Complete weekly cycle

After Learning Completes

The system:

1. Freezes the discovered entity list as your Asset Group
2. Transitions discovery_mode to false
3. Begins active monitoring — alerts fire when assets go silent
4. You can review and adjust the auto-created Asset Group anytime

Re-Discovery

You can re-enable discovery mode on an existing pulse to detect new assets. The system will merge newly discovered assets into the existing group.