> For the complete documentation index, see [llms.txt](https://docs.inspector.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inspector.dev/concepts/alerts.md).

# Alerts

Create alerts to monitor your application processes.

### Introduction

Alerts empowers developers to catch complications before they develop into problems, and helps you preserve high availability and deliver high quality of service.

It also assists you in making informed decisions about the present and the future, serves as input to automation of infrastructures and, most importantly, is an indispensable learning tool.

![Alerts list](https://2873457055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ51SrLj6qvIRejC1XD%2Fuploads%2FCfWCK0z7ESJKrFeWTM1h%2Falerts-list.png?alt=media\&token=df68026a-0f8e-416d-a17f-e163594e1faf)

### Create an alert

The most important part of the alert creation form is "Query & Metric".

![Alert form](https://2873457055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ51SrLj6qvIRejC1XD%2Fuploads%2F3DfYX1RB4lwRMQSXOM82%2Fcreate-alert.png?alt=media\&token=b91a072e-2fba-4afd-962d-aed0dcf12c80)

### Query

Define what resource you want monitor (Transactions or Segments) and the query you want perform to identify the target items.

### Metric

As a metric you can choose from a various analytic functions like count, min, max, or the average value.  The execution time or memory consume are the available metrics. You could limit this value directly in the metric so in that case you should select the count option to match the number of events within the condition specified in the query.

### Threshold

Threshold represents **when** you want receive an alert. Different conditions allows you to detect different anomalous behaviors. For any type of threshold you can read a short description of their typical use cases.

{% hint style="warning" %}
**Note**

You need to turn on **Alert** notifications in your notification channels, in order to be notified for threshold violations.
{% endhint %}


---

# 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.inspector.dev/concepts/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.