Monitor a server and send email alerts

Enable monitoring

1. 01Open a server and choose Notifications from its left navigation. The Metrics and health section starts open.
2. 02Install MihraOps Agent, or update it when the page reports an older version.
3. 03Enable server monitoring and choose the CPU, memory and disk thresholds.
4. 04Save. Confirm that host metrics, Docker health and threshold rules report a healthy running state.

The samples, rule state and incident history stay in the bounded Agent data directory on your own server. They are not uploaded to the MihraSoft backend.

What becomes an incident

The default rules cover sustained high CPU and memory, disk warning and critical levels, an unreachable Docker daemon, failed container inspection, unhealthy containers and restarting containers.

A single bad sample does not send email. Each rule has a required duration and a separate recovery period so short spikes and flapping do not create a mail storm. The Agent records one open transition and one recovery transition per incident.

Connect Gmail or another SMTP account

1. 01Open Email delivery and choose Gmail (recommended) or Other SMTP.
2. 02For Gmail, enable 2-Step Verification on your Google Account, create a 16-character password for MihraOps on the App Passwords page, and enter it with your Gmail address. Do not use your normal Google Account password.
3. 03For another provider, use the host, port, TLS/STARTTLS mode and any username/password or app password from its SMTP setup page.
4. 04Set the From name/address, message language, server label and up to 20 recipients.
5. 05Save, then request a test email.

The password never returns to the renderer and is not written to the settings JSON. It travels through SSH standard input and is encrypted on your server with the existing MihraOps secret key. The Gmail API tab only explains OAuth requirements in this version; it is not an active delivery method.

Read delivery history correctly

The Agent queues each incident, recovery and test separately per recipient. Temporary failures use bounded exponential retries; permanent credential, TLS or SMTP rejection failures are recorded without retrying forever.

A “sent” record means the SMTP server accepted the message. It does not prove final inbox placement, so verify the real recipient inbox and spam folder during setup.

The blind spot

An Agent running on a server cannot report that same server losing all power or network access, nor can it report its own process and Docker service dying together. Those cases require an independent observer outside the server.

MihraOps Agent notifications are an operational aid, not an emergency monitoring service or an SLA.