> 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.3/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.4-set-up-an-smtp-server-for-opencrvs-monitoring-alerts.md).

# 3.3.4 Set up an SMTP server for OpenCRVS monitoring alerts

We use [Elastalert](https://elastalert.readthedocs.io/en/latest/), in tandem with ElasticSearch and Kibana to monitor the health of the OpenCRVS stack in production.

In order for OpenCRVS to alert your Technical System Administrator of any memory or hardware issues, we have set up email notifications as the Elastalert option. Therefore you should have an [SMTP service](https://www.wpbeginner.com/showcase/best-smtp-service-providers-with-high-email-deliverability/) setup. You can read more about monitoring OpenCRVS [here](https://github.com/opencrvs/documentation/blob/release-v1.3.0/setup/7.-monitoring).

[Google offers SMTP services for free](https://kinsta.com/blog/gmail-smtp-server/) linked to a Gmail account, but there are countless other paid for SMTP services such as [SendGrid](https://sendgrid.com/) or [Mailchimp](https://mailchimp.com/).

You will need to take note of your **SMTP host, port, username,** **password** & your **Technical System Administrator's email address** for the entering as Github Secrets in [section 3.3.6 Deploy](/v1.3/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.6-deploy-automated-and-manual.md). We have hardcoded the service to use SMTP **SSL by default**.


---

# 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://documentation.opencrvs.org/v1.3/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.4-set-up-an-smtp-server-for-opencrvs-monitoring-alerts.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.