> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/tools/get-alerts.md).

# Alerts

JFrog Connect sends alerts about your devices. For a device resource or process, you just need to configure an alert channel, such as email or webhook, and define the alert threshold.

In JFrog Connect, you can create alerts that will inform you about various states and resource usage of your devices. For example, you can set a trigger to send you an alert whenever a device has used more than 80% of its disk space.

Creating an alert trigger requires the following procedures:

1. **Prepare Channel Type**: Create an email account or a [webhook URL](/features-new-ui/tools/get-alerts/create-channel/set-webhook.md#webhook-url) that will be used in your channel configuration.
2. [**Create Channel**](/features-new-ui/tools/get-alerts/create-channel.md): Configure the channel in which you will receive alerts.
3. **Create Alert**: Define the type of alert and a threshold for triggering the alert. This procedure is described below.

## Create Alert

To create an alert, go to Alerts in the left navigation tree and click Create Alert.

<div align="left"><figure><img src="https://1679291640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOX8HIrQ8f257lv49Od1Z%2Fuploads%2FZobBvaFQlojzYqmHJDF4%2Falerts-01-nui.png?alt=media&amp;token=42222462-653c-4746-b3ab-34be7f0eea1a" alt=""><figcaption></figcaption></figure></div>

Complete the following information:

* **Alert Name**: Enter a name to help you remember what this alert is for.
* **Channels**: Choose an alert channel from the list and click Apply. You can add multiple channels. If there are no channels in the list, click Create Channel and define one.&#x20;
* **Alert Trigger**: Choose whether the alert will be triggered by a device resource or a process on the device.
  * **Trigger Condition**: Define the threshold that will trigger an alert. For example, an alert on a resource might be: CPU > 80%.
* **Apply On**: Choose the devices the alert will be applied to. You can choose criteria for selecting the devices to be monitored, or you choose specific devices.

After choosing the information above, create the new alert.

<div align="left"><figure><img src="https://1679291640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOX8HIrQ8f257lv49Od1Z%2Fuploads%2FlB3WKRqQWiylU0sKFWeZ%2Falerts-02-nui.png?alt=media&amp;token=7e8f84b8-25d8-4508-a37a-b8ff3f52a205" alt="" width="375"><figcaption></figcaption></figure></div>

## What’s Next?

Learn how to [create a channel](/features-new-ui/tools/get-alerts/create-channel.md) on which you will receive alerts.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.connect.jfrog.io/features-new-ui/tools/get-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
