User-Defined
Threshold Rules
Updated May 31, 2026 · today
Custom alert conditions on any query, with cooldown and duration guards. Use when you need a hand-tuned alert beside automatic detection.
Example alert
user-defined: error_rate > 5% for 3 minutes (checkout-service)
Exact wording varies — the detector generates titles from the anomaly it finds. This is representative of what an alert looks like when it fires.
How it works
You define a LogsQL query, a numeric threshold, and a duration window. The rule evaluates on a configurable interval (default: 60s). Cooldown prevents re-fire within a suppression window. No learning period — fires as configured.
Availability
Runs on these tiers:
trialteamgrowthenterprise
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- Composite Rules
Multi-condition alert rules combining several signals. Use when no single threshold captures the failure mode.