Telemetry
Threshold alerts

Notify people when a queryable signal moves outside its expected range

Create threshold alerts from Explore or SQL results, evaluate complete time-series points on a schedule, and deliver actionable context to email recipients.

Outcomes

  • Alert on customer-impacting failures, latency, cost, or missing data.
  • Use several recent points to reduce noise from a single incomplete bucket.
  • Connect every threshold to a specific investigation or response.

How it works

A reviewable workflow from signal to decision

1

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.

2

Set volume and time safeguards

Avoid ratios on tiny denominators, allow for normal scheduling jitter, and ignore incomplete time buckets where appropriate.

3

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

Count, sum, average, min, max, and percentile conditions
Greater-than and less-than comparisons
Configurable evaluation interval and recent-point window
Optional exclusion of the newest incomplete bucket
Multiple email recipients and alert history

See the analysis

SQL recipes that use this capability

Start with one production workflow

Use a focused prompt, send synthetic events, and verify the first useful query before expanding coverage.

Open prompt pack