> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Schedule Alert
> Set up alerts that notify you automatically when your data crosses a threshold you define.
The **Schedule Alert** page is where you create and manage automated alerts that notify you when your data crosses a threshold you've defined — for example, when an error rate spikes or a deployment fails. This page lives under **Administration → Scheduler → Schedule Alert** in the left sidebar.
At the top of the page, two tabs let you switch between:
* **Alerts** — the view covered in this guide, listing every alert you've scheduled.
* **Reports** — scheduled reports, covered separately in the **Schedule Report** guide.
The count next to the **Alerts** tab (e.g. "5") shows how many alerts currently exist.
## Viewing existing alerts
The table on the **Alerts** tab lists every alert that has been set up, along with when it last ran and whether it's currently active.
| Column | What it shows |
| ---------------- | ------------------------------------------------------------------------------------ |
| **Last Run** | The date and time this alert's query was last checked. |
| **Name** | The alert's name, with a short description underneath explaining what it monitors. |
| **Schedule** | How often the alert runs (for example, "Every 1 hour", "Daily at 8:00 AM"). |
| **Notification** | Icons showing which channels (e.g. email, Slack) this alert notifies when triggered. |
| **Owners** | Avatar of the user (or users) responsible for this alert. |
| **Active** | A toggle to instantly turn the alert on or off without editing it. |
| **Actions** | An **✏️ Edit** button to open and modify the alert's configuration. |
Use the **Search by name** box to find a specific alert, and the **All statuses** and **All owners** dropdowns to filter the list — for example, to show only active alerts or only alerts owned by a specific person. The bottom of the table shows a count such as **"Showing 1–5 of 5 alerts"** to confirm how many results are displayed.
## Creating a new alert
Click **+ Schedule Alert** in the top right of the page to open the **Schedule New Alert** form.
### General Information
| Field | Required | Details |
| --------------- | -------- | ------------------------------------------------------------------------------------------ |
| **Alert Name** | Yes | A unique name so you can identify this alert later (for example, "High Error Rate Alert"). |
| **Description** | No | A short explanation of what this alert monitors, for your own and your team's reference. |
### Query Configuration
This section defines what data the alert checks and when it should fire.
| Field | Required | Details |
| ---------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Query** | Yes | The SQL query the alert will run on its schedule (for example, `SELECT count(*) FROM errors WHERE created_at > NOW() - INTERVAL '1 hour'`). The result of this query is what gets compared against your threshold. |
| **Trigger Type** | Yes | How the alert should evaluate the query result — for example, **Threshold**, which fires when the result crosses a value you set. |
| **Operator** | Yes | The comparison to apply to the query result (for example, **GREATER THAN**). |
| **Threshold** | Yes | The value that triggers the alert when the query result meets the condition set by the Operator (for example, `100`). |
### Schedule Configuration
This section defines how often the query above should be checked.
| Field | Required | Details |
| ----------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Schedule Type** | Yes | How the alert's check should be scheduled — for example, **Recurring (every)**, which repeats on a fixed interval as defined below. |
| **Timezone** | Yes | The timezone the schedule should run in (for example, **UTC**). |
| **Frequency** | Yes | How often the query should run, made up of two parts: **Every** (the interval, e.g. Day, Hour, Minute) and **At** (the specific time the check should run, e.g. `13:15:08`). |
### Notification Methods
This section controls who gets notified, and how, when the alert triggers.
**Notification Channels** (required) — check one or more of **Email**, **Slack**, or **Teams**. You must select at least one channel to receive alert notifications.
Selecting a channel adds a settings card for it below, where you configure that channel's specific details. Each card shows an **Active** badge and an **✕** to remove that channel from the alert.
For **Email**, the **Email Settings** card asks for:
| Field | Required | Details |
| ------------------ | -------- | ----------------------------------------------------------------------------------------------------------- |
| **Email Subject** | Yes | The subject line the notification email will be sent with (for example, "Alert: High Error Rate Detected"). |
| **Recipient** | Yes | The primary email address the alert notification should be sent to. |
| **CC Recipients** | No | Additional email address(es) to CC on the notification. |
| **BCC Recipients** | No | Additional email address(es) to BCC on the notification. |
Slack and Teams show their own settings card, with fields specific to those channels, once checked — the layout follows the same pattern as the Email Settings card above.
Once all required fields (marked with a red **\***) are filled in, click **Save Alert** in the top right to create the alert. Click **Cancel** to discard your changes and return to the Alerts list.