What a Monitor Contains
- Name
time_periodreport_typesource_idsai_routingdestination_idswindow_hoursenabled
Key Capabilities
- Create and update monitors
- Trigger runs manually
- Inspect runs, logs, and events
- Cancel a running job
How to Use It
- Configure sources, providers, and destinations first
- Create a monitor and choose its sources and destinations
- Set providers for
filter,keywords,global_summary, andreport - Save and run it, then inspect runs and logs
Report Type Relationship
daily: ongoing monitoringweekly: periodic summariesresearch: longer-form research output
Related API
- List and create:
GET /api/v1/monitors,POST /api/v1/monitors - Default AI routing:
GET /api/v1/monitors/ai-routing/defaults - Run:
POST /api/v1/monitors/{monitor_id}/run - Logs:
GET /api/v1/monitors/{monitor_id}/logs - Runs:
GET /api/v1/monitors/{monitor_id}/runs - Cancel:
POST /api/v1/monitors/{monitor_id}/runs/{run_id}/cancel - Events:
GET /api/v1/monitors/{monitor_id}/runs/{run_id}/events - Update and delete:
PATCH /api/v1/monitors/{monitor_id},DELETE /api/v1/monitors/{monitor_id}
Recommended Workflow
- Validate a small source set first
- Confirm destination output before enabling long-form monitors
- If a run stalls, inspect runs first, then events and logs