Deploying an Alerta Server

Let’s get started by installing the Alerta server, the web console and doing some basic configuration and customisation.



The server is based on the most recent stable Ubuntu cloud image, Ubuntu 16.04 LTS (Xenial). The Alerta server will be installed to run as a uWsgi application proxied behind an nginx web server. The web console will be served from the same nginx server and configured to support Basic Auth logins.

Customisation will involve defining a new alert severity called “Fatal” that will be black in colour, and allowing an additional alert environment called “Code” in addition to “Production” and “Development”.


Before you begin, ensure you are familiar with the Ubuntu/Debian operating system, that you have “super user” privileges (ie. a root user login) and remote ssh access to the server you are deploying to.

Step 1: Install Packages

To install MongoDB 3.2 run the following commands:

$ sudo apt-key adv --keyserver hkp:// --recv EA312927
$ echo "deb xenial/mongodb-org/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.2.list
$ sudo apt-get update -y && sudo apt-get upgrade -y
$ sudo apt-get install -y mongodb-org

Configure MongoDB to run via systemd and start at boot:

$ sudo vi /etc/systemd/system/mongodb.service
Description=High-performance, schema-free document-oriented database

ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf


Start the MongoDB server, check it is running and set it to start on reboot:

$ sudo systemctl start mongodb
$ sudo systemctl status mongodb
$ sudo systemctl enable mongodb

To run Alerta we need to ensure all Python 3 dependencies are installed:

$ sudo apt-get install -y python3 python3-setuptools python3-pip python3-dev python3-venv
$ sudo apt-get install -y nginx uwsgi-plugin-python3

To install the Alerta server and alerta command-line tool into a Python 3 virtual environment run:

$ cd /opt
$ python3 -m venv alerta
$ alerta/bin/pip install --upgrade pip wheel alerta-server alerta uwsgi

To install the web console run:

$ cd /var/www/html
$ wget -q -O - | sudo tar zxf -
$ sudo mv alerta*/app/* .

Step 2: Configuration

Create a wsgi python file, uWsgi configuration file and systemd script:

$ sudo vi /var/www/
from alerta import app

The uwsgi server mounts the Alerta API on /api, logs to syslog and uses a unix socket to communicate with the nginx web server:

$ sudo vi /etc/uwsgi.ini
chdir = /var/www
mount = /
callable = app
manage-script-name = true
env = BASE_URL=/api

master = true
processes = 5
logger = syslog:alertad

socket = /tmp/uwsgi.sock
chmod-socket = 664
uid = www-data
gid = www-data
vacuum = true

die-on-term = true

Create a systemd configuration file for the uwsgi server:

$ sudo vi /etc/systemd/system/uwsgi.service
Description=uWSGI service

ExecStart=/opt/alerta/bin/uwsgi --ini /etc/uwsgi.ini


Start the uwsgi server, check the current status and enable it to start on reboot:

$ sudo systemctl start uwsgi
$ sudo systemctl status uwsgi
$ sudo systemctl enable uwsgi

Configure nginx to serve Alerta as a uWsgi application on /api and the web console as static assets.


Mounting the Alerta API on /api and serving the web console static assets from the same domain avoids any problems with CORS or HTTPS mixed content errors.

$ sudo vi /etc/nginx/sites-enabled/default
server {
        listen 80 default_server;
        listen [::]:80 default_server;

        location /api { try_files $uri @api; }
        location @api {
            include uwsgi_params;
            uwsgi_pass unix:/tmp/uwsgi.sock;
            proxy_set_header Host $host:$server_port;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        location / {
                root /var/www/html;

Restart nginx so that it picks up the new configuration:

$ sudo service nginx restart

Modify the existing web console config.json configuration file to set the endpoint to /api:

$ sudo vi /var/www/html/config.json
{"endpoint": "/api"}

At this point you should be able to view the web console on port 80 in your web browser.

Step 3: Customisation

Firstly, generate a random string:

$ cat /dev/urandom | tr -dc A-Za-z0-9_\!\@\#\$\%\^\&\*\(\)-+= | head -c 32 && echo

Assign the random string to the SECRET_KEY sever setting:

$ vi /etc/alertad.conf

Add a new severity level called “Fatal” as the highest possible severity and remove some unwanted severity levels:

$ vi /etc/alertad.conf
    'fatal': 0,
    'critical': 1,
    'warning': 4,
    'indeterminate': 5,
    'ok': 5,
    'unknown': 9

And change the color map to reflect the new severities:

    'severity': {
        'fatal': 'blue',
        'critical': 'red',
        'warning': '#1E90FF',
        'indeterminate': 'lightblue',
        'ok': '#00CC00',
        'unknown': 'silver'

Configure the default “reject” plugin to allow the additional alert environment called “Code” and not just “Production” or “Development”:

$ vi /etc/alertad.conf
ALLOWED_ENVIRONMENTS=['Production', 'Development', 'Code']

Make sure you restart uwsgi so that the Alerta API picks up the new severity and plugin configurations:

$ sudo service uwsgi restart

To use the command-line tool to submit a test alert you first need to create a configuration file that defines what API endpoint to use:

$ vi $HOME/.alerta.conf
endpoint = http://localhost/api

Send a test “fatal” alert and confirm it has been received by viewing it in the web console:

$ /opt/alerta/bin/alerta send --resource net01 --event down --severity fatal \
--environment Code --service Network --text 'net01 is down.'

Note that the above can be shortened by using argument flags instead of the full argument names:

$ /opt/alerta/bin/alerta send -r net01 -e down -s fatal -E Code -S Network -t 'net01 is down.'

To view the alerts in a terminal run:

$  /opt/alerta/bin/alerta query

Next Steps

After you deploy your Alerta server, you might want to try some of the following tutorials: