bigdata_simulate_monitor

​

Overview

• Flash (default): previews one recent window. No dates, no novelty check, and no email
• Full: replays the monitor’s scheduled runs over a past period

​

When to Use

• Checking a new monitor: Running a flash preview after bigdata_create_monitor and before activating
• Checking an edit: Previewing the effect of new queries, entities, or schema
• Backtesting: Replaying the schedule over a past period to see what the monitor would have caught

​

How It Works

1. Call bigdata_simulate_monitor with the monitor id, and a mode and dates for a full simulation
2. Keep the returned simulation_id and mode
3. Read the results with bigdata_get_monitor_runs, passing the same simulation_id and mode

​

Parameters

{"id": "b0253b18-0dd8-4a01-a9a4-f209bce91a26"}

{
  "id": "b0253b18-0dd8-4a01-a9a4-f209bce91a26",
  "mode": "full",
  "start_timestamp": "2026-11-01T00:00:00Z",
  "end_timestamp": "2026-11-04T00:00:00Z"
}

​

Important Notes

• Flash does not accept dates. Sending start_timestamp or end_timestamp with flash returns an error
• Full requires end_timestamp
• A full simulation can cover at most 90 runs. The API’s rejection of the period is returned as the error
• A full simulation emails its result if the monitor already has email delivery set. Flash never sends email
• An unknown monitor id returns a not-found error

​

Data Returned

{
  "simulation_id": "019a6a4e-8f3c-7b21-9d4e-2f1a6c0b5e77",
  "mode": "full",
  "status": "PENDING",
  "retention_warning": null,
  "runs_requested": 12
}

​

Practical Tips

​

Start with flash

​

Watch the retention warning