Skip to main content
The Snowflake and BigQuery alerts cover the common cost anomalies. When you need something specific to your setup, write a custom alert: a SQL query that fires when it returns any rows.
The Radar custom alert editor: available Snowflake fields on the left, generated SQL in the editor, a Test alert button and Slack and email destinations

​
Create one

On the alerts page for your warehouse, click Create alert.
  1. Name and describe the alert so the notification says something useful when it fires.
  2. Write the SQL, or describe what you want in plain language and click Generate SQL to have Paradime draft it. The draft lands in the editor, where you can read and change it before saving. The left pane lists the fields available to you, such as QUERY_HISTORY and WAREHOUSE_METERING_HISTORY, with the type of each column.
  3. Test alert runs the query immediately and shows whether it would fire, along with sample rows, so you are not waiting for a schedule to find out you had a typo.
  4. Choose how often it repeats: Alert daily while true keeps reminding you each day the condition holds, Alert once until it resets tells you once and stays quiet until the condition clears.
  5. Pick destinations: a Slack channel, a Microsoft Teams webhook, or email, the same way Bolt notifications are configured.
The contract. The query runs on your own warehouse and must be a single SELECT over the views listed in the left pane, automatically limited to the last 30 days. Any row it returns fires the alert, so write it to return nothing when everything is fine and the offending rows when it is not.

​
Live alerts

Saved custom alerts appear under the built-in list on the same page, each with an enable switch, its destinations, its repeat setting, and a 30-day history strip showing which days it fired, which days it was evaluated without firing, and any days evaluation failed. Custom alerts are evaluated on the same schedule as the built-in Radar alerts.