Alerts, the server page and platform security

MotoDealerHQ checks its own health every 10 minutes. Problems open an alert, which is emailed and shown as a banner across the platform console until it clears. The Server page gives the full picture, and the Security page covers sign-ins, sessions and locked accounts.

How alerts work #

1. Every 10 minutes a scheduled task runs the health checks below.
2. A new warning or critical problem opens an alert and emails it to the alert address in the control panel (or, if none is set, to every active platform owner). Info-level alerts aren't emailed.
3. The alert stays open while the problem persists. A banner at the top of every platform console page shows how many alerts are open and how many are critical.
4. When the problem clears, the alert is resolved and a short "resolved" email goes out.

If an alert email fails, it is retried on the next run.

What is checked #

Work with alerts #

1. Open Operations › Alerts.
2. Open lists each alert's severity, problem and start time (UTC).
3. Select Acknowledge to show the team someone is on it. The alert stays open until the problem actually clears.
4. Resolved recently lists alerts that cleared, with their start and end times.

The Server page #

Open Operations › Server. A box at the top lists anything that needs attention, or says "All checks pass".

• Disk: percentage used and free space for each monitored disk.
• Backups: when the last nightly backup finished (the job runs at 02:15 UTC and keeps 14 days of files), the database dump and media archive sizes, and an overdue badge if it is late.
• Database: MySQL version, total size and the largest tables.
• Background work: jobs by status and the oldest waiting time, permanent failures in 24 hours, application errors in the last hour and day, and each scheduled task with its interval, last run and result (a late badge when it is behind).
• Logs and versions: PHP version, environment, deployed code version and log file sizes. Logs rotate daily and are kept 30 days.
• Maintenance: turn maintenance mode on or off.
• Housekeeping: Run health checks now, Clean up old records now and Clear caches.

Maintenance mode #

1. On Operations › Server, under Maintenance, optionally enter a Message shown to visitors.
2. Select Turn maintenance mode on and confirm.
3. Every dealer console, dealership website and the API now shows a maintenance page with your message. The platform console and the payment and SMS webhooks keep working.
4. When you're done, select Turn maintenance mode off.

While it's on, an info-level alert reminds everyone.

Related operations pages #

• Operations › Jobs: filter background jobs by status and type, see payloads and errors, and retry dead or failed jobs (jobs.manage).
• Operations › Errors: application errors with secrets removed. Dealers who hit an error see a reference id you can look up here.
• Operations › Import health and DMS health: inventory import and DMS connector results across dealerships.
• Operations › Usage: platform usage and growth figures.

Platform security #

Open Security & settings › Security.

• Two-factor sign-in: the policy in force for platform staff and dealership users, and a list of dealership owners who haven't turned two-factor sign-in on yet.
• Locked or repeatedly failing accounts: the account, its kind (platform or dealership user), failed attempts and lock expiry. Select Unlock to clear a lock.
• Active sessions (last 24 hours): platform staff sessions, with Sign out to end one.
• Recent platform sign-ins.

Security & settings › Audit log lists every platform staff action, optionally filtered by dealership.

Tips #

• Set a shared alert address (a team inbox) in the control panel so alerts don't depend on one person.
• After restarting the worker or fixing cron, select Run health checks now to clear stale alerts straight away.
• Check Backups after any server change, and make sure copies leave the server.

Permissions #

Limitations #