> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/alerts/creating-and-editing-alert-rules/alert-rules-for-devices.md).

# Alert Rules for Devices

{% hint style="info" %}
**Note:** This page describes how to configure alerts for **Device Layer** monitoring (network infrastructure devices like routers and switches monitored via SNMP).

If you are looking to configure alerts for **Connected Devices** (CPE, home routers, and other endpoints), please see our documentation on [Alerts for Connected Devices](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-alerts).
{% endhint %}

## Prerequisites

This section assumes that you have gone through the [device discovery process](https://docs.thousandeyes.com/product-documentation/device-layer/discovering-device-layer-devices), and are using the ThousandEyes platform to monitor one or more devices.

Once ThousandEyes is monitoring devices, you may want to configure alerts based on device-layer data.

## Device-Layer Alert Rules

To create an alert rule for the device layer, go to the [**Manage > Alert Rules > Devices**](https://app.thousandeyes.com/manage/alerts/rules/?tab=Device) tab and click **Add New Alert Rule**.

![](/files/sWPfQzctsDDE8aIChcl1)

The sections below describe the fields on **Add New Alert Rule** screen.

### Primary Section

* **Alert Type**: Select **Device** or **Interface**.
* **Rule Name**: Give the alert rule a human-readable name that makes sense for your implementation of ThousandEyes.

### Settings Tab

* **Devices**: Select the devices that this alert rule should apply to. After you click the dropdown, you can search for devices by name.

  A device's *name* is its SNMP name, or the name you changed it to after the device-discovery process. For more information, see [Device Discovery](https://docs.thousandeyes.com/product-documentation/device-layer/discovering-device-layer-devices#device-discovery) and [Device-Discovery Results](https://docs.thousandeyes.com/product-documentation/device-layer/device-discovery-results).
* **Alert Conditions**: Set the alert conditions that must be met in order to trigger this alert rule. The available alert conditions vary depending on the alert type you have specified.

### Notifications Tab

The **Notifications** tab works the same regardless of the alert type you are setting up. You can find information about how to use the **Notifications** tab in [Alert Notifications](https://docs.thousandeyes.com/product-documentation/alerts/alert-notifications).

### Additional Resources

For information on custom-built integrations for alerts in ThousandEyes, see [Custom-Built Integrations](https://docs.thousandeyes.com/product-documentation/integration-guides/custom-built-integrations).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thousandeyes.com/product-documentation/alerts/creating-and-editing-alert-rules/alert-rules-for-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.