> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.9/setup/7.-monitoring/7.4-setting-up-alerts.md).

# 9.4 Setting up alerts

All alerts and thresholds can be managed through **Management -> Stack Management -> Alerts and Insights -> Rules and Connectors.** OpenCRVS comes with a set of preconfigured alerts, but we recommended these alerts be customised to your country's needs.

Currently, OpenCRVS supports email alerts out of the box. Other types are available by customising your country config package.

#### **Preconfigured alerts**

| Type  | Description                                    | Rule  |
| ----- | ---------------------------------------------- | ----- |
| Alert | CPU load on any node                           | >70%  |
| Alert | Service error                                  | >0    |
| Alert | Available disk space on encrypted data storage | <30 % |

### Setting up a new alert

Basic instructions for setting up alerts can be found from Kibana documentation under [Alerts and rules](https://www.elastic.co/guide/en/kibana/master/apm-alerts.html#apm-alerts).

It is important to use "Index" as the connection type when setting up new alerts. This option instructs Kibana to write alerts to an Elasticsearch index from where other tools can get notified about errors happening in the system.

![](https://3485090019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRziAMaeBMeyiTg5hfFq5%2Fuploads%2Fgit-blob-41e758663f9e0fa14a10fe555b67c8cabba425b0%2Fimage%20\(14\).png?alt=media)

Our alerting tool [Elastalert2](https://github.com/jertel/elastalert2) reads alerts from a preconfigured index named `kibana-alert-history-default` and is configured to send an email to `ALERT_EMAIL` email address. This email address can be changed as part of [deployment](/v1.9/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.6-deploy-automated-and-manual.md).

![](https://3485090019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRziAMaeBMeyiTg5hfFq5%2Fuploads%2Fgit-blob-ef671b5e02a13a1aef9749be18c7cf11c60a777f%2Fimage%20\(32\).png?alt=media)

**Read more:**

* [Alerting](https://www.elastic.co/guide/en/kibana/current/alerting-getting-started.html)
* [APM - Alerts and rules](https://www.elastic.co/guide/en/kibana/master/apm-alerts.html#apm-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://documentation.opencrvs.org/v1.9/setup/7.-monitoring/7.4-setting-up-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.