# Create alert rules and links
The Monitoring page in the Redox dashboard allows you to view and manage your traffic alert rules. [Learn about monitoring data exchange health](https://docs.redoxengine.com/permalink/RqjicoYocYtUDfFmaaoSt/#monitor-data-exchange-health).
> **Traffic alert rules vs. Redox system alerts**
>
> Remember that traffic alert rules are unique rules you create to proactively monitor your integration health.
>
> System alerts also monitor integration health, but they’re Redox-managed and Redox-resolved. [Learn about Redox system alerts](/how-to-use-redox/check-redox-system-alerts).
## Prerequisites
- All environment users can view traffic alert rules. However, a user must be assigned to an **engineer** or a **support** role to manage alert rules. [Learn about user roles](/basics/managing-access-for-your-redox-organization/what-are-user-roles).
- You must have a paid Redox account to use alert rules. If you have a free Redox account, alert rules won’t be visible in the dashboard or available via API.
## Overview
Review the types of alert rules and the purpose of links before you start creating.
### Types of alert rules
There are different traffic alert rule types that watch for different scenarios in your data exchange. You can create one or more types based on your unique needs.
No traffic alert rule
A No traffic alert rule monitors whether traffic is flowing appropriately in a given subscription.
With this type of alert rule, you receive a notification when no logs reach a terminal state (i.e., `Succeeded`, `Filtered`, `Failed`) during a given time period (i.e., as little as 30 minutes up to 72 hours).
This type of alert isn’t meant for tracking errors since failed logs count as completed traffic.
> **Pending logs not included**
>
> This doesn’t include pending logs since they aren’t in a terminal state.
Low traffic alert rule
A Low traffic alert rule monitors whether traffic is flowing as anticipated in a given subscription.
With this type of alert rule, you receive a notification if less than X number of logs reach a terminal state (i.e., `Succeeded`, `Filtered`, `Failed`) within a specified time (i.e., as little as 30 minutes up to 72 hours).
This type of alert rule is one step more preemptive than a no traffic alert type since it can help you catch an unexpected dip in traffic before reaching no traffic at all. However, it still isn’t meant for tracking errors since failed logs count as completed traffic.
> **Pending logs not included**
>
> This doesn’t include pending logs since they aren’t in a terminal state.
Error threshold alert rules
An Error Threshold alert rule monitors the number of errors in a given subscription.
With this type of alert rule, you receive a notification if X number of logs reach a terminal state of `Failed` and will no longer be retried within a specified time (i.e., as little as 15 minutes up to 24 hours).
Retry threshold alert rule
A Retry threshold alert rule monitors the number of retries for any log in a given subscription.
With this type of alert rule, you receive a notification if one or more logs has been retried more than X number of times within 15 minutes (this is a static lookback time).
For example, if you configure an alert rule with a retry threshold of 10, the alert rule triggers if one or more logs have reached at least 10 retries within the last 15 minutes. These logs might continue retrying, but the alert rule doesn’t clear until all logs for the linked subscription reach a terminal state or have fewer than 10 retries within 15 minutes.
> **What’s not included**
>
> A Retry threshold alert doesn’t measure the cumulative number of retries for all logs combined, nor does it measure the number of individual logs that are retrying.
### What an alert rule link means
You must link an alert rule to a subscription to actively watch for the rule’s defined conditions. If the conditions are met, you receive a notification. That way, you can preemptively monitor the health of your subscriptions.
An alert rule can be linked to multiple subscriptions. You can pause or delete a link at any time.
If an alert rule isn’t linked, it’s not actively monitoring anything. You can see if an alert rule has any subscription links on the Monitoring \> Alert rules tab of the dashboard.
*Alert rule without subscription links*
## View alert rules and statuses
1. Log in to the Redox dashboard.
2. From the navigation menu, click the **Monitoring** page.
3. By default, the Alert rules tab opens with any configured alert rules and their latest status (statuses won’t display if there aren’t any subscription links). If linked to multiple subscriptions, the status is a global one.
*Global statuses of linked alert rules*
> **Available environment types and connections**
>
> If you see a warning message instead a list of alert rules or a New button:
>
> - Make sure you’re not in a development environment. Alert rules are only available in staging or production environments.
> - Check if you have any connections configured for the staging or production environment. If not, [request a new connection](/how-to-use-redox/manage-your-redox-setup/request-a-connection-or-subscription) for the environment first.
4. Search for or use the filters to narrow down the list of displayed alert rules.
5. Click the **subscription** **links** to expand the alert rule to see each individual subscription links and status.
*Expanded details of alert rules*
> **Alert statuses**
>
> Individual statuses display for each alert rule link:
>
> - Okay: Traffic in the subscription hasn’t met the conditions defined by the alert rule. This means the alert rule hasn’t ever been triggered or was resolved after being triggered previously.
> - Triggered: Traffic in the subscription has met the conditions defined by the alert rule. An alert notification has been sent to the designated users, unless it was triggered during an ignored day.
> - Unknown: The subscription isn’t being actively monitored. This can happen if the alert rule was recently created and hasn’t run yet.
> - Paused: The subscription isn’t being actively monitored because a user in your Redox organization has paused the alert rule. Only monitoring is paused, not actual traffic flow of the subscription.
>
> Individual link statuses are evaluated to create a global status for the alert rule. If all links have the same status, the global status matches.
>
> - Okay: No links have triggered alerts.
> - Triggered: At least one link has a triggered alert.
> - Paused: All links have a paused status.
> - Unknown: All links have an unknown status or a combination of Unknown and Paused.
6. To review a specific alert rule, click anywhere its **row** to open the Details page.
## Create an alert rule
1. Follow the steps to view alert rules.
2. Click the **New** button.
3. The create form opens. Under Alert settings, fill out the details:
1. Name: Enter a **human-friendly name** for the alert rule. This name displays on the Alert rules tab, so choose a descriptive enough name to easily identify it.
2. Type: Select one of the following:
- **No traffic**
- **Low traffic**
- **Error threshold**
- **Retry threshold**
> **Multiple alert rules for a subscription**
>
> It’s possible to create multiple alert rules of the same type for a given subscription. For example, you could link two different No traffic alert rules to one subscription. However, you’d then receive multiple notifications for the same type of issue at potentially different times.
3. Within (only for No traffic, Low traffic, Error threshold): Select the **time interval** for the **look-back window** Redox should use when checking for the alert rule conditions.
Retry threshold alerts uses a static look-back, so this field won’t appear.
No traffic or Low traffic - Supported time intervals
For No traffic or Low traffic alert rules, select any of these time intervals:
- 30 minutes
- 1 hour
- 2 hours
- 6 hours
- 12 hours
- 24 hours
- 48 hours
- 72 hours
Error threshold - Supported time intervals
For Error threshold alert rules, select any of these time intervals:
- 15 minutes
- 30 minutes
- 1 hour
- 2 hours
- 6 hours
- 12 hours
- 24 hours
4. Number of logs or errors (only for Low traffic, Error threshold, Retry threshold): Use the **up and down arrows** to choose the allowable **number of logs or errors** before an alert rule is triggered.
*Create an alert rule*
5. (_Optional_) Skip notifications on: Select any **days of the week** or **holidays** you don’t want to receive notifications for triggered alert rules.
> **Monitoring doesn’t stop on skipped days**
>
> Monitoring doesn’t ever stop—only _notifications_ stop on skipped days. Any triggered alerts still display in the dashboard no matter what.
>
> Let’s say you select Saturday and Sunday as your skipped days. If an alert rule is triggered on Saturday morning, you won’t get a notification about it, but it will appear in the dashboard. On Monday, you might get a notification when the triggered alert resolves.
>
> Also keep in mind that you might not find out about a triggered alert if it’s both triggered and resolved on a skipped day, unless you happen to check the dashboard while it’s active.
> **Multi-region holiday lists**
>
> The holiday list changes depending on the region of the currently selected Redox organization. If you have a multi-region organization, you’ll see holiday lists for both the U.S. and Canada.
1. Select a **time zone** for the skipped days.
> **Default time zone for different subscriptions**
>
> The **default** time zone is your connection’s time zone (i.e., in their Redox organization settings). If your connection doesn’t specify a time zone, U.S. Central time serves as the default.
>
> If an alert rule is linked to subscriptions with different time zones, notifications are triggered based on the respective time zone of each subscription.
>
> For example, you might have an alert rule that’s linked to subscriptions in Central and Pacific time, but you chose to skip notifications on Saturday. If the alert is triggered at 12:30 AM Eastern on a Saturday, you’ll still receive a notification for both subscriptions because it’s only 11:30 PM Central or 9:30 PM Pacific on a Friday. However, if another alert rule is triggered for both subscriptions just an hour later, you’d only get a notification for the second subscription.
4. Under Notifications, enter the **email address(es)** that should receive a notification when the conditions of the alert rule are met. Use commas to separate email addresses if the alert notification should go to more than one address.
5. Click the **Create** button.
6. A modal opens with a reminder to link the alert rule to activate it. Click the **Confirm** button.
*Configure notification settings*
7. The Details page opens. To start monitoring rule conditions, [link an alert rule](https://docs.redoxengine.com/permalink/39Lf3qtqeHmCZkFaKf5jKz/#link-an-alert-rule) to one or more subscriptions.
## Edit an alert rule
1. Follow the steps to view alert rules.
2. Find the alert rule you want to edit and click anywhere in its **row.**
3. The Details page opens. Click the **Edit** button.
4. The edit form opens. Edit the alert rule name, type, time intervals, skip notifications, or notification email addresses.
5. Once you’re finished, click the **Save** button.
*Edit an alert rule*
## Delete an alert rule
1. Follow the steps to view alert rules.
2. Find the alert rule you want to delete**.** Click the t**hree-dots** icon, then the **Delete** option. Deleting an alert rule also deletes any associated subscription links.
Alternatively, click anywhere in its **row** to open the Details page to review any details prior to deleting. Click the **Delete** button.
> **Deleting alert rule vs. deleting links**
>
> This is different from the delete options for each alert rule link, which you can find in the table of links.
3. A confirmation modal appears. Click the **Delete** button to continue.
*Delete an alert rule*
## Link an alert rule
Once you’ve created an alert rule, you must link it to one or more subscriptions to begin monitoring for the rule’s conditions.
> **Linking the same alert twice**
>
> You can link one alert rule to multiple subscriptions. You can also have one subscription with multiple links. However, you can’t link the same alert rule to the same subscription more than once.
1. Follow the steps to view alert rules.
2. Find the alert rule you want to link and click anywhere in its **row.**
3. The Details page opens. Under the Alert rule links section, select the relevant **connection** from the drop-down menu.
4. Click the **Select subscription** link.
5. A modal opens with the available subscriptions for the connection you selected. Use the Search field or the Connection drop-down to narrow down the available options. If needed, use the page options at the bottom of the modal to navigate through the pages. Then select the **radio button** of the subscription you want to link an alert rule to.
6. Click the **Select** button.
7. Click the **Link rule** button to finish linking the alert rule to the subscription.
*Link an alert rule*
8. The new link appears in the table. Redox begins evaluating for the alert rule conditions every **15 minutes** (Error threshold or Retry threshold alert rules) or every 30 minutes (No traffic or Low traffic alert rules).
9. Repeat these steps to link the alert rule to as many other subscriptions as needed.
10. When the alert rule conditions are met, we send a notification to the specified list of email addresses. The notification includes the information and related links for the triggered alert rule.
> **Redox email address**
>
> The alert notification is sent from `alerts@redoxengine.com`. Make sure to allow-list that email address as a sender, or check your spam folder if the alert notification doesn't show up in your inbox.
*Triggered alert email notification*
The specified users also receive a notification when the triggered condition resolves.
*Resolved alert email notification*
## Pause an alert rule link
Pausing a link temporarily halts subscription monitoring. The alert rule is still linked to the subscription, but Redox won’t watch for any of the specified conditions. Pausing only affects monitoring, not actual subscription traffic.
1. Follow the steps to view alert rules.
2. Find the alert rule with the link you want to modify**.** Click the **subscription links** to expand it.
3. Click the **Pause** button next to the subscription link.
*Option 1: Pause an alert rule link*
4. Alternatively, you can click in the **alert rule row** to open the Details page. Under the Alert rule links section, you can pause subscription links.
*Option 2: Pause an alert rule link*
5. To resume monitoring in either location, click the **Resume** button.
*Resume monitoring a subscription link*
## Delete an alert rule link
Deleting a link removes the subscription from the alert rule, meaning the subscription won’t be monitored anymore. Deleting the link doesn’t delete the alert rule itself, though.
1. Follow the steps to view alert rules.
2. Find the alert rule with the link you want to delete and click anywhere in its **row.**
3. Under the Alert rule links section, click the **three-dots icon**, then the **Delete** option next to the relevant subscription link.
4. A confirmation modal opens. Click the **Delete** button to confirm and successfully delete the alert rule link.
*Delete an alert rule link*
> **Platform API endpoints**
>
> This article describes how to manage traffic alert rules in the **Redox dashboard**. To manage alert rules via **API**, use these **Redox Platform API** endpoints instead:
>
> - [Create alert rule](https://docs.redoxengine.com/permalink/fc31e290-f81a-52c0-a697-eed528b3ecde-create-alert-v-2)
> - [Update alert rule](https://docs.redoxengine.com/permalink/c1f1667f-7bb5-5166-bc93-bfb70e41ae27-update-alert-v-2)
> - [Delete alert rule](https://docs.redoxengine.com/permalink/3d921228-18ab-5417-a6dc-b3fac9e895d3-delete-alert-v-2)
> - [Create link](https://docs.redoxengine.com/permalink/865472af-f08c-50c5-8bc5-6acc206c3733-create-link-v-2)
> - [Update link](https://docs.redoxengine.com/permalink/20147b12-a464-5489-9a30-f8c4b8ca7ea0-update-link-v-2)
> - [Delete link](https://docs.redoxengine.com/permalink/2c7429ec-3a23-5283-b64c-355d55bf044e-delete-link-v-2)