Goal
Balance detection speed, output quality, and usage cost for your workload.Shared Tuning Principle
Start from a reliable condition, then adjust only one parameter at a time.- Validate stream with Validate Stream
- Validate condition with Check Once
- Launch monitor or digest
- Review runtime output via Get Job Details
- Iterate
Live Monitor Levers
interval_seconds
How often condition checks run.
- lower values: faster detection, higher usage
- higher values: slower detection, lower usage
Condition quality
Precise conditions reduce false triggers and wasted reruns. Guide: Writing Reliable ConditionsLive Digest Levers
window_minutes
How much time each summary covers.
- shorter windows: more frequent summaries
- longer windows: fewer summaries
capture_interval_seconds
How often frames are sampled.
- lower intervals: richer detail, higher usage
- higher intervals: lower usage, less detail
max_windows
Optional cap on number of summary windows per job.
Starting Profiles
Fast incident detection (live-monitor)
Balanced digest (live-digest)
Cost-controlled digest (live-digest)
Common Mistakes
- Skipping
check-oncebefore long runs - Changing multiple parameters at once
- Using vague conditions that inflate noise
Next Steps
- Delivery mode selection: Choose Your Workflow
- Troubleshooting: Debugging Playbook
- Runtime field semantics: Get Job Details