Getting Started - Database Setup

EndPoint Monitor uses MySQL for holding most of its configuration and operational data, although any compatible database engine such as MariaDB should also work. You can either use an existing database or give EndPoint Monitor its own dedicated database. Names of all objects all contain a prefix of EPM_ to help operate in shared databases.

Users

Only the controllers you set up requires access to the database, agents fetch their data through the controllers. The controllers usually require two users for the database you intend to use, and 'admin' user that has access to modify the database schema, indexes and keys, used for automatic setup and upgrades, and a 'normal' user that is used for the rest of the application's operation. The 'admin' user is optional if manually setting up and maintaining your database.

Example of creating a specific database for your EndPoint Monitor installation:

CREATE DATABASE IF NOT EXISTS endPointMonitor;

Example of creating an admin user to manage your EndPoint Monitor upgrades:

CREATE USER IF NOT EXISTS 'endPointMonitorAdmin'@'%' IDENTIFIED BY '%adminPassword%' PASSWORD EXPIRE NEVER;
GRANT SELECT, UPDATE, INSERT, DELETE, ALTER, CREATE, DROP, INDEX, REFERENCES ON endPointMonitor.* TO 'endPointMonitorAdmin'@'%';

Example of creating a normal application user for your EndPoint Monitor installation:

CREATE USER IF NOT EXISTS 'endPointMonitorUser'@'%' IDENTIFIED BY '%password%' PASSWORD EXPIRE NEVER;
GRANT SELECT, INSERT, UPDATE, DELETE ON endPointMonitor.* TO 'endPointMonitorUser'@'%';

Schema

There are two supported methods of setting up your database schema. The recommended approach is to allow your EndPoint Monitor controller during setup to automatically initialise it. Alternatively you can download the manual setup script from https://download.smnt.co.uk/endPointMonitor/sql/mysql_setup.sql and run this against your database, making sure you swap out the passwords for values only you know.