> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom alerts

> Write your own Radar alert as SQL over your warehouse metrics, generate it from a description with AI, test it, and route it to Slack, Teams, or email.

The [Snowflake](/products/radar/real-time-alerting/snowflake-alerts) and [BigQuery](/products/radar/real-time-alerting/bigquery-alerts) alerts cover the common cost anomalies. When you need something specific to your setup, write a **custom alert**: a query over your Radar metrics that fires when it returns any rows.

## 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 let Paradime draft it for you. The draft lands in the editor, where you can read and change it before saving. The left pane lists the tables and columns the built-in alerts read; clicking one inserts it at your cursor.
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**: *daily while true* keeps reminding you each day the condition holds, *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](/products/bolt/creating-schedules/notification-settings) are configured.

<Info>
  The rule is simply: **any row the query returns is a violation**. Write the query so it returns nothing when everything is fine, and returns the offending rows when it is not.
</Info>

## 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.


## Related topics

- [Radar cost controls: budgets, usage groups, custom alerts](/changelog/2026-09-09/radar-cost-controls.md)
- [Real-time Alerting](/products/radar/real-time-alerting/index.md)
- [Changelog](/changelog/overview.md)
- [Radar](/products/radar/index.md)
- [Alerts Configuration and Customization](/integrations/elementary-data/sending-alerts/alerts-configuration-and-customization.md)