---
title: "Alert Policies"
slug: "alert-policies-1"
description: "Manage your organization's alert policies in the Kentik portal. Learn to add, edit, and debug policies for effective policy-based alerting."
updated: 2026-02-09T18:55:51Z
published: 2026-02-09T18:55:51Z
---

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

# Alert Policies

This article discusses the **Alert Policies** page of the Kentik portal. For more information about policy-based alerting, first read these articles:

- [**Policy Alerts Overview**](/v1/docs/policy-alerts-overview)
- [**Policy Templates**](/v1/docs/alert-policy-templates)
- [**Alerting**](/v1/docs/alerting)
- [**Notifications**](/v1/docs/notifications)
- [**Mitigations**](/v1/docs/mitigations)
- [**Policy Settings**](/v1/docs/alert-policies#policy-settings)

> [!NOTE]
> **Note:** Alert policy configuration can be complex. Please reach out for help from our support team (see [**Customer Care**](/docs/alert-policies-1#)).

![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(277).png)

*Manage your organization's alert policies from the Alert Policies page.*

## Alert Policies Page

The Alert Policies page is where you manage alert policies for Kentik’s alerting system (see [**Alerts and Policies**](/v1/docs/policy-alerts-overview#alerts-and-policies)).

To access the page:

1. Go to Settings » **Alerting**and click **Manage Policies**.
2. The [**Policies List**](/v1/docs/alert-policies#policies-list) shows your organization’s available alert policies. You can add, enable/disable, clone, delete, or edit policies from this list.

> [!NOTE]
> **Note:** While admin-level users can see and use all of the controls listed throughout this article, member-level users can only:
> 
> - See and filter the policies displayed in the **Policies** list.
> - Open a policy’s [**Policy Details Drawer**](/v1/docs/alert-policies#policy-details-drawer).
> - Enable or disable policies.

### Alert Policies Page UI

The Alert Policies page contains the following UI elements:

- **Alert Policy Templates**(button): Opens the [**Policy Templates**](/v1/docs/alert-policy-templates) page to manage templates and add a policy from a template (see [**Add Policy from Template**](/v1/docs/alert-policies#add-policy-from-template)).
- **Policies statistics**(fields): Shows the number of policies created and enabled in your organization, along with the maximum allowable number for each.
- **Add Alert Policy**(button): Performs two actions:
  - Add Alert Policy: Opens the [**Add Alert Policy Dialog**](/v1/docs/alert-policies#add-alert-policy-dialog), where can create a new NMS or Classic Threshold policy from scratch.
  - Add Policy from Template: Click the down arrow and select [**Add Policy from Template**](/v1/docs/alert-policies#add-policy-from-template)****to create a new policy from a template.
- **Filters** (funnel icon): Toggles the **Filters** pane between expanded and collapsed.
- **Search**(field): Narrows the list of policies based on matches with the entered text. Also displays any filters applied with the **Filters** pane.
- **Filters**(pane): A set of [**Policy Filters**](/v1/docs/alert-policies#policy-filters) to narrow the list of alert policies.
- **Policies**(list): Lists your organization’s policies (see [**Policies List**](/v1/docs/alert-policies#policies-list)).
- **Policy Details** (drawer): Click a policy to open a summary of its settings (see [**Policy Details Drawer**](/v1/docs/alert-policies#policy-details-drawer)).

### Policies List

The Policies list is a table showing all available alert policies in your organization. It includes columns for policy information and actions.

- **Select All** (in header row): Click to select all policies in the list. Click again to deselect all policies.
- **Selected**: Check the boxes to select policies, causing the [**Selected Policy Controls**](/v1/docs/alert-policies#selected-policy-controls) to appear above the Policies list.
- **Status**: The policy’s status (Disabled or Enabled).
- **Type**: The policy type, one of NMS, Traffic, Cloud, or Protect (see [**Policy Types**](/v1/docs/policy-alerts-overview#policy-types)).
- **ID**: The unique policy ID assigned by Kentik.
- **Name**: The user-specified policy name. The user-specified description, if entered, is shown below the name.
- **Data Sources**: The network entities covered by the policy, as specified on the **Dataset** tab in [**Policy Settings**](/v1/docs/alert-policies#policy-settings).
- **Metrics**: The units (e.g., bits/s, packets/s) by which the alert measures incoming flow data (see [**Data Funneling**](/v1/docs/threshold-policy-settings#data-funneling)). The primary metric is listed first, followed by secondary metrics (if any).
- **Dimensions**: The policy dimensions that define a key for traffic subdivision (see [**About Keys**](/v1/docs/policy-alerts-overview#about-keys)****and [**Dimensions Reference**](/v1/docs/metrics-dimensions#dimensions-reference)).
- **Used by Tenant**: The [**My Kentik Portal**](/v1/docs/my-kentik-portal) tenants using the policy (“None” if not used).
- **Actions**(menu): Click the vertical dots icon to open the [**Policy Action Menu**](/v1/docs/alert-policies#policy-action-menu).

#### Selected Policy Controls

When one or more policies are selected, these controls appear above the **Policies** list:

- **Add/Edit Labels**: Click to open the [**Labels**](/v1/docs/labels)****settings page, where you can create, edit, or remove labels for the selected policies.
- **Clear Labels**: Clears all applied labels from the selected policies.
- **Apply Labels**: Select one or more labels to apply them to all selected policies. Click outside to close the dropdown.
- **Enable/Disable**: Enable or disable all the selected policies.
- **Delete**: Opens a**Delete Policies** dialog to confirm or cancel removal of the selected policies.
- **Add Notification Channels**: Opens the [**Add Notification Channels**](/v1/docs/alert-policies#add-notification-channels) dialog, where you assign one or more notification channels to the selected policies.
- **Policies selected**: Displays the number of selected policies.

![With policies selected, controls for applying labels and adding notification channels appear at the top.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(278).png)

With policies selected, controls for applying labels and adding notification channels appear at the top.

#### Add Notification Channels

The **Add Notification Channels** dialog lets you assign one or more notification channels to the selected policies. It has the following:

- ![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/AP-Add_notif_dialog.png)**Close**(button): Click the **X** in the upper right to close the dialog without saving changes.
- **Notification Channels** (field): Shows lozenges for any assigned notification channels. The lozenge to the left of each channel name indicates the channel's type.
  - Remove: Click the **X** in a channel’s lozenge to remove it.
  - Add: Click in the field to select a channel from the filterable channel list.

> [!NOTE]
> **Notes**:
> 
> - Channels already assigned to this policy are not included in the list.
> - Disabled channels are included but can’t be selected.
- **Add New Channel**: Opens the**Add Notification Channel** dialog (see [**Notification Settings**](/v1/docs/notifications#notification-settings)) to create a new channel and automatically add it to the selected policies.
- **Test Notification Channels**: Sends a test notification to all assigned channels. Present only when **Notification********Channels** is populated.
- **Cancel**: Exits the dialog without changing channel assignments.
- **Continue**: Saves current channel assignments and exits.

#### Policy Action Menu

Access the Action menu for each policy via the vertical dots in either the [**Policies List**](/v1/docs/alert-policies#policies-list),****at the right of each policy's row, or the the [**Policy Details Drawer**](/v1/docs/alert-policies#policy-details-drawer), at the right of the policy title.

The menu includes these options:

- ![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(280).png)**Edit Policy**: Edit [**Policy Settings**](/v1/docs/alert-policies#policy-settings) on the Edit Policy page.
- **Enable/Disable Policy**: Enables or disables a policy.
- **Clone Policy**: Starts a new policy pre-populated with settings from an existing policy (see [**Clone a Policy**](/v1/docs/alert-policies#clone-a-policy)).
- **Delete**: Confirm deletion of a policy.
- **Debug**: Opens the [**Policy Debug Dialog**](/v1/docs/alert-policies#policy-debug-dialog) with the top keys for both current traffic and baseline data.

### Policy Filters

Filter policies in the **Policies** list using the **Filters** pane on the left. By default, all policies are shown. Click the checkboxes to narrow the list by policy **Type** and/or **Status.**

The Filters pane includes:

- ![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(281).png)**Close**: Click the **<** in the upper right to close the pane. Click the funnel icon to show it again.
- **Reset to default**: Clears all current filters (appears only when filters are specified).
- **Type**: Check the policy type boxes (NMS, Traffic, Cloud, or Protect) to restrict the list (see [**Policy Types**](/v1/docs/policy-alerts-overview#policy-types)).
- **Status**: Check policy status boxes (Enabled and/or Disabled) to restrict the list.
- **Policy ID**: Enter a complete policy ID to filter the list to only that policy (no partial matching).

### Policy Details Drawer

The Policy Details drawer is a read-only display of policy settings, including details not displayed in the **Policies** list. Click on a policy row to open its details drawer. Click the same row again to close the drawer. The drawer contains the following elements:

- ![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(282).png)**ID number**: The unique ID assigned when the policy was created.
- **Name**: The user-specified policy name.
- **Actions**: A vertical dots icon that opens the Action menu (see [**Policy Action Menu**](/v1/docs/alert-policies#policy-action-menu)).
- **Status**: A lozenge indicating the policy’s status (enabled: green, disabled: gray).
- **Description**: The user-specified policy description.
- **Policy Dashboard** (not present for NMS policies): The dashboard name associated with the policy, if any (see [**General Policy Settings**](/v1/docs/threshold-policy-settings#general-policy-settings)). A lozenge labeled Preset indicates the dashboard is a Kentik-provided preset.
- **Dataset**(pane)**:** Summarizes the policy’s **Dataset** settings (see [**Policy Dataset Settings**](/v1/docs/threshold-policy-settings#policy-dataset-settings)).
- **Thresholds**(pane): Summarizes the policy’s **Thresholds** settings (see [**Policy Threshold Settings**](/v1/docs/threshold-policy-settings)). The number in brackets indicates the number of thresholds.
- **Baseline** (pane): Summarizes the policy’s **Baseline** settings (see [**Policy Baseline Settings**](/v1/docs/threshold-policy-settings#policy-baseline-settings)).

### Policy Debug Dialog

The **Debug** dialog provides context to understand why a threshold in an alert policy triggered an alarm (see [**About Alert Thresholds**](/v1/docs/threshold-policy-settings#about-alert-thresholds)). The included table presents information about a policy from two perspectives:

- **Current Traffic**: Shows information about the top-X keys (see [**About Keys**](/v1/docs/policy-alerts-overview#about-keys)) for the policy in current traffic. Current traffic is the set of flow records and associated traffic data in the most recently completed aggregate.
  - The duration of each aggregate is determined by the policy’s **Evaluation Frequency** setting.
  - The number of keys is defined by the **Maximum Number of Keys** (the actual number of keys may be less depending on the **Minimum Traffic Threshold** setting).
- **Baseline Data**: The table shows information related to the top-X keys in the baseline data of the same policy (see [**About Historical Baselines**](/v1/docs/threshold-policy-settings#about-historical-baselines)).

> [!NOTE]
> **Notes**:
> 
> - The Debug dialog is only available for enabled policies.
> - See [**Policy Settings Pages**](/v1/docs/alert-policies#policy-settings-pages) for more about threshold policy settings.

![The debug dialog provides details about the top keys in either current or baseline traffic.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/AP-Debug_current.png)

The debug dialog provides details about the top keys in either current or baseline traffic.

#### Policy Debug Dialog UI

The **Debug** dialog has the following UI elements:

- **Close**: Click the **X** in the upper right to close the dialog.
- **Top Keys**: Choose from the drop-down which top-X keys to show in the **Debug** list, either **Current Traffic** or **Baseline Data**.
- **Debug list**: A table showing info about top-X keys (current or baseline) for the selected policy (see [**Debug Current Columns**](/v1/docs/alert-policies#debug-current-columns) and [**Debug Baseline Columns**](/v1/docs/alert-policies#debug-baseline-columns)).

> [!NOTE]
> **Note:** If insufficient traffic is available for debugging, a message replaces the Debug list:
> 
> - Current traffic: “No matches found” means no traffic or no traffic for the policy to evaluate.
> - Baseline data: “No baseline data available” means no traffic or the baseline is still building.

#### Debug Current Columns

The **Current Traffic** view of the **Debug** list includes the following columns:

- **Position** (#): The ordinal position of the key in the top-X current keys for this policy.
- **Keys**: The policy’s key as defined in the **Dimensions** setting (see [**Data Funneling**](/v1/docs/threshold-policy-settings#data-funneling)).
- **Entries**: The total number of flows with this key in the current traffic data aggregate.
- **Primary Metric**: The policy’s Primary Metric value, which determines the position of the key in the top-X (see [**Data Funneling**](/v1/docs/threshold-policy-settings#data-funneling)).
- **Metric 2**: The policy’s first Secondary Metric value, if any (see [**Data Funneling**](/v1/docs/threshold-policy-settings#data-funneling)).
- **Metric 3**: The policy’s second Secondary Metric value, if any (see [**Data Funneling**](/v1/docs/threshold-policy-settings#data-funneling)).
- **First seen**: The start time of the current traffic data aggregate.

> [!NOTE]
> **Note**: The start time is in either UTC or local time depending on the **Time Zone** selected in your User Profile (see [**User-specific Defaults**](/v1/docs/user-profile#userspecific-defaults)).

#### Debug Baseline Columns

The**Baseline Data** view of the **Debug** list includes the following columns:

- **Position** (**#**): The ordinal position of the key in the top-X baseline keys for this policy.
- **Keys**: The policy’s key as defined in the policy’s **Dimensions** setting (see [**Data Funneling**](/v1/docs/threshold-policy-settings#data-funneling)).
- **Entries**: The total number of flows with this key in the baseline data.
- **Value**: A percentile value, e.g. P95, for the policy’s Primary Metric. Determines the key’s position in the top-X (see [**Building the Baseline**](/v1/docs/threshold-policy-settings#building-the-baseline)).
- **Min Value**: The lowest one-hour rollup aggregation value for the policy’s Primary Metric over the “baseline window” (see [**Building the Baseline**](/v1/docs/threshold-policy-settings#building-the-baseline)).
- **P50 Value**: The 50th percentile value of the policy’s Primary Metric over the “baseline window.”
- **Max Value**: The highest one-hour rollup aggregation value for the Primary Metric over the “baseline window.”
- **Chosen Time**: The timestamp of the first flow record matching the key.

## Adding a Policy

Follow these steps to add an alert policy in Kentik.

> [!NOTE]
> **Note:** To add a policy, your assigned RBAC roles must have permissions equivalent to those of an Administrator or Super Administrator (see [**Kentik-managed Roles**](/v1/docs/kentik-rbac#kentikmanaged-roles)).

### Policy Creation Methods

Add an alert policy in the Kentik portal using any of the following methods:

- **From Scratch**:
  - On the [**Alert Policies Page**](/v1/docs/alert-policies#alert-policies-page), click**Add Alert Policy**.
  - Select either an NMS (see [**NMS Policy Settings**](/v1/docs/nms-policy-settings)) or Classic Threshold (see [**Threshold Policy Settings**](/v1/docs/threshold-policy-settings)) policy and proceed to the settings page to create the new policy.
- **From Data Explorer (Classic Threshold only)**:
  - In the Data Explorer subnav, select **Create Alert Policy** from the **Actions** drop-down (see [**Add a Query-based Policy**](/v1/docs/alert-policies#add-a-querybased-policy)).
  - A policy settings page, pre-populated with your query settings and with policy type **Traffic** pre-selected, opens to create the new policy (see [**Threshold Policy Settings**](/v1/docs/threshold-policy-settings))
- **From Policy Template**:
  - On the [**Alert Policies Page**](/v1/docs/alert-policies#alert-policies-page),****use the subnav controls to start a new policy from a pre-configured template (see [**Use a Policy Template**](/v1/docs/alert-policies#use-a-policy-template)).
- **Clone Existing Policy**:
  - In the [**Policies List**](/v1/docs/alert-policies#policies-list),****click the vertical dots icon for a policy and select **Clone Policy** (see [**Clone a Policy**](/v1/docs/alert-policies#clone-a-policy)).
  - A policy settings page, pre-populated with settings from the cloned policy, opens to create the new policy.

### Add Alert Policy Dialog

The **Add Alert Policy** dialog offers two options: creating an **NMS** or **Classic Threshold** policy. Once you select your preferred policy, you’ll be redirected to the corresponding settings page.

The dialog, which opens from the **Add Alert Policy** button on the [**Alert Policies Page**](/v1/docs/alert-policies#alert-policies-page), includes:

- ![Choose an NMS or Classic Threshold policy type and finalize settings of a new alert policy.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/AP-Add_policy_dialog.png)**NMS**: Click to select an NMS policy, which alerts you when devices, interfaces, or BGP neighbors are in an unhealthy state (see [**NMS Policy Settings**](/v1/docs/nms-policy-settings)).
- **Classic Threshold** (default): Click to select a Classic Threshold policy, which alerts you when selected metrics pass specified thresholds (see [**Threshold Policy Settings**](/v1/docs/threshold-policy-settings)).
- **Cancel**: Click **Cancel** at lower right or **X** in the upper right to exit the dialog without saving.
- **Continue**: Click to proceed to a [**Policy Settings**](/v1/docs/alert-policies#policy-settings-pages) page to finalize details of the new policy.

### Add a Query-based Policy

A query-based alert policy is time-limited and built from contextual Data Explorer queries. You create it directly in Data Explorer using your current data view criteria (dimensions, metrics, filters).

> [!NOTE]
> **Note:** Query-based policies are Traffic type (see [**Policy Types**](/v1/docs/policy-alerts-overview#policy-types)).

To create a query-based alert policy:

1. ![Menu options including 'Create Alert Policy' highlighted in the actions dropdown.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/AP-add-query-based-policy.png)In [**Data Explorer**](/v1/docs/data-explorer), create a query using the **Query** sidebar settings (data sources, dimensions, metrics, filters, etc.).
2. In the subnav, choose**Create Alert Policy** from the **Actions** drop-down to create a new policy on the Add Query-Based Policy page. The policy’s settings are populated automatically from the Data Explorer query.
3. On the **General** tab, provide a name for the policy.
4. On the **Thresholds** tab, click**Edit Conditions** and add at least one condition (see [**Threshold Conditions**](/v1/docs/threshold-policy-settings#threshold-conditions)).
5. Check the [**Policy Summary Pane**](/v1/docs/threshold-policy-settings#policy-summary-pane) for missing fields or errors.
6. Click **Save**to create the new policy and return to Data Explorer.

> [!NOTE]
> **Note**: Editing a query-based policy after it appears in the **Policies** list removes its expiration.

### Clone a Policy

Clone an alert policy to duplicate it for modification without altering the original:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. From the Actions menu (vertical dots) for the policy, choose **Clone Policy**. This takes you to the Clone Policy page, where the settings of a new policy will be populated with the values of the cloned policy.
3. Change the name/description of the new policy as necessary.
4. Finalize other settings and click **Save** to create the new policy.

### Use a Policy Template

Kentik provides preconfigured policies as templates to cover many common alerting needs.

There are two ways to add a policy from a template using the [**Alert Polices**](/v1/docs/alert-policies#alert-policies-page) page:![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(288).png)

- **Alert Policies page**: Click the drop-down on the **Add Alert Policy** button and select [**Add Policy from Template**](/v1/docs/alert-policies#add-policy-from-template). Choose a template and click **Continue**.
- **Policy Templates page**: Click the Policy Templates button and click the Clone icon on a template.

Both methods open an Add Alert Policy page with default settings from the template. Tailor the settings to your needs and save the new policy (see [**Policy Settings**](/v1/docs/alert-policies#policy-settings)).

> **Note:** Templates should not be used as-is, but should be customized to your network and traffic situation.

#### Add Policy from Template

The **Add Alert Policy from Template** dialog includes the following:

- ![Adding an alert policy for high BPS between internal VMs in AWS.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/AP-Add_from_template_dialog.png)**Cancel** (buttons): Click the **X** in the upper right or **Cancel** at lower left to exit the dialog without saving.
- **Drop-down menu**: Click to choose an existing template from the list.
- **Go to Policy Templates**: Opens the Policy Templates page (see [**Policy Templates**](/v1/docs/alert-policy-templates)).
- **Template description**: A description of what the template is designed to detect.
- **Continue** (button): Opens the Add Alert Policy page, pre-populated with the chosen template’s settings.

> [!NOTE]
> **Note:**The **Continue** button is inactive until you select a policy template.

## Policy Settings

The pages and dialogs used to specify policy settings are discussed here.

> [!NOTE]
> **Note:** For specifics about the policy settings UI, see [**NMS Policy Settings**](/v1/docs/nms-policy-settings)****and [**Threshold Policy Settings**](/v1/docs/threshold-policy-settings).

### Policy Settings Pages

Alert policy settings can be accessed on the following pages:

| Page | Use to… | Locations |
| --- | --- | --- |
| **Add Alert Policy** | Configure a new policy from scratch or via template | Alert Policies page, **Add Alert Policy** button and **Add Alert Policy from Template** dialog. |
| **Edit Policy** | Edit an existing policy | Alert Policies page, **Edit Policy** in the [**Policy Action Menu**](/v1/docs/alert-policies#policy-action-menu). |
| **Clone Policy** | Duplicate an existing policy | Alert Policies page, **Clone Policy** in the [**Policy Action Menu**](/docs/alert-policies-1#Ga08-Policy_Action_Menu). |
| **Add Query-Based Policy** | Create a policy from Data Explorer****query settings | [**Data Explorer**](/v1/docs/data-explorer) page, **Create Alert Policy** in the **Actions** menu in the subnav. |

### Policy Settings Page UI

The policy settings pages share the same layout and the following common UI elements:

- **Help**: Click the **?** icon button in the subnav to open the Alert Policies KB article in a new tab.
- **Cancel**(button): Exits with saving changes and returns you to the Alert Policies page.
- **Create** or **Save**(button): Saves policy settings and returns you to the Alert Policies page. Active only when all settings are complete and error-free (see [**Policy Summary Pane**](/v1/docs/threshold-policy-settings#policy-summary-pane)).
- **Settings tabs** (not present in NMS policies): Tabs for making policy settings (see [**Threshold Settings Tabs**](/v1/docs/threshold-policy-settings#threshold-settings-tabs)).
- **Summary pane** (not present in NMS policies): Expand/collapse a summary of each tab’s settings. Also indicates completion status (see [**Policy Summary Pane**](/v1/docs/threshold-policy-settings#policy-summary-pane)).

> [!NOTE]
> **Note:** The **Cancel** and **Create** or **Save** buttons are located at the upper right except for NMS policies, where they are at the bottom of the page.

## Manage Alert Policies

Follow these steps to manage alert policies in the Kentik portal.

> [!NOTE]
> **Note:** See also [**Add a Query-based Policy**](/v1/docs/alert-policies#add-a-querybased-policy), [**Clone a Policy**](/v1/docs/alert-policies#clone-a-policy), and [**Use a Policy Template**](/v1/docs/alert-policies#use-a-policy-template).

### Add an NMS Policy

To create an NMS alert policy using the Alert Policies page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click**Add Alert Policy** at the upper right.
3. Select **NMS** and click **Continue.**
4. Specify the settings (see [**NMS Settings Page**](/v1/docs/nms-policy-settings#addedit-nms-alert-policy-page)).
5. Click **Save** to save the policy and return to the Alert Policies page.

### Add a Classic Threshold Policy

To create a Classic Threshold alert policy using the Alert Policies page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click**Add Alert Policy**at the upper right.
3. Select **Classic Threshold** and click **Continue.**
4. On the Add Alert Policy page, specify the settings on each tab:
  1. General: See [**General Policy Settings**](/v1/docs/threshold-policy-settings#general-policy-settings).
  2. Dataset: See [**Policy Dataset Settings**](/v1/docs/threshold-policy-settings#policy-dataset-settings).
  3. Thresholds: See [**Policy Threshold Settings**](/v1/docs/threshold-policy-settings#policy-threshold-settings).
  4. Baseline: See [**Policy Baseline Settings**](/v1/docs/threshold-policy-settings#policy-baseline-settings).
5. Click **Save** to save the policy and return to the Alert Policies page.

### Add an NMS Threshold Policy

To create an NMS threshold alert policy using the Alert policies page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click**Add Alert Policy**at the upper right.
3. Select **Classic Threshold** and click **Continue.**
4. On the Add Alert Policy page, specify the settings on each tab:
  1. General:
    1. Select **NMS** from the **Policy Type** selector.
    2. Adjust other settings (see [**General Policy Settings**](/v1/docs/threshold-policy-settings#general-policy-settings)).
  2. Dataset:
    1. Specify settings covered in [**Dataset NMS Settings**](/v1/docs/threshold-policy-settings#dataset-nms-settings).
    2. Adjust other settings (see [**Policy Dataset Settings**](/v1/docs/threshold-policy-settings#policy-dataset-settings)).
  3. Thresholds:
    1. Specify settings covered in [**Thresholds NMS Settings**](/v1/docs/threshold-policy-settings#thresholds-nms-settings).
    2. Adjust other settings (see [**Policy Threshold Settings**](/v1/docs/threshold-policy-settings#policy-threshold-settings)).
  4. Baseline: Specify the settings covered in [**Policy Baseline Settings**](/v1/docs/threshold-policy-settings#policy-baseline-settings).
5. Click **Save** to save the policy and return to the Alert Policies page.

### Edit a Policy

To edit an alert policy using the Alert Polices page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click the vertical dots icon for a policy and select **Edit Policy**.
3. Update policy settings.
4. Click **Save** to save your changes and return to the Alert Policies page.

> **Note**: For details on available settings, see [**NMS Policy Settings**](/v1/docs/nms-policy-settings)****and [**Threshold Policy Settings**](/v1/docs/threshold-policy-settings).

### Disable or Enable a Policy

To enable or disable an alert policy using the Alert Policies page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click the vertical dots icon for a policy and select either:
  1. Disable Policy: The policy will no longer monitor its dataset, generate alerts, or trigger mitigations.
  2. Enable Policy: The policy will resume its normal functions.

### Remove a Policy

To remove an alert policy using the Alert Policies page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click the vertical dots icon for a policy and select **Remove.**
3. Click **Remove**to confirm deletion of the policy.

### Debug a Policy

To debug an enabled alert policy using the Alert Policies page:

1. Choose Settings » **Alert Policies**from the portal's main nav menu.
2. Click the vertical dots icon for a policy and select **Debug**.

> [!NOTE]
> **Note**: You can also select **Debug** from the **Action** menu in a policy’s [**Policy Details Drawer**](/v1/docs/alert-policies#policy-details-drawer).
3. Select **Current Traffic** or**Baseline Data** from the dropdown.

> [!NOTE]
> **Note:** When insufficient traffic is available for debugging, a message will display in place of the **Debug** list (see [**Policy Debug Dialog UI**](/v1/docs/alert-policies#policy-debug-dialog-ui)).
