How it works
A reviewable workflow from signal to decision
Choose a signal with an owner
A threshold is useful only when someone understands what it means and can act. Begin with a user, revenue, or reliability outcome.
Set volume and time safeguards
Avoid ratios on tiny denominators, allow for normal scheduling jitter, and ignore incomplete time buckets where appropriate.
Test the response path
Trigger the condition with synthetic data, confirm delivery, and include enough context for the recipient to open the right query or dashboard.
Capabilities
What is included
See the analysis
SQL recipes that use this capability
Detect Missing Service Heartbeats
Find services, workers, or scheduled tasks that stopped reporting before a failure event appeared.
Open recipeFind Stalled Background Jobs With SQL
Join job start and finish events to identify work that exceeded its expected completion window.
Open recipeCalculate API Error Rate by Route
Use SQL to rank API routes by 5xx error rate while protecting the result from low-volume noise.
Open recipeStart with one production workflow
Use a focused prompt, send synthetic events, and verify the first useful query before expanding coverage.