Device logs and alerts
ISPMan gives you two ways to keep an eye on your hardware: logs (what the router says is happening) and offline alerts (a router has stopped checking in).
Device logs
Section titled “Device logs”Turn on remote logging
Section titled “Turn on remote logging”A MikroTik sends its logs to ISPMan only when remote logging is on.
- Open the router’s device page.
- Click Remote Logging. A cross on the button means it’s off; a tick means it’s on.
- Click Enable Remote Logging. To stop, open it again and click Disable Remote Logging.
Remote logging helps you troubleshoot: login failures, interface flaps, DHCP problems and errors all arrive in one place.
All devices: Devices → Logs
Section titled “All devices: Devices → Logs”Devices → Logs (/dashboard/devices/logs) lists log events from every
device in your account.
| Column | Meaning |
|---|---|
| Timestamp | When the event happened. |
| Device / Device Type | Which router sent it. |
| Device IP | The address it came from (filterable). |
| Severity | How serious the message is (filterable, sortable). |
| Log Type | The kind of log message (filterable). |
| Message | The log text (filterable). |
One router: View Logs
Section titled “One router: View Logs”On a device page, click View Logs (/dashboard/devices/mikrotik/<id>/logs)
for a live stream from that router. New lines appear as they arrive.
- Select date range to look back at a specific period.
- Type in the search box to filter by message, level, IP or facility.
- Click a line to open Log Entry Details: timestamp, log type, message, device IP, protocol, facility, priority, severity, the raw log line, and when it was received.
If you see “No logs found for this device”, check that Remote Logging is on.
Offline alerts
Section titled “Offline alerts”Set up alerts
Section titled “Set up alerts”Go to Settings → Alerts (/dashboard/settings/alerts). Owners set this up.
- Under Device Alerts, switch on Enable Device Alerts. You’ll be notified when devices go offline or come back online.
- Choose an Alert Delay: After 5 minutes offline (the default), After 10 minutes offline or After 30 minutes offline. A longer delay avoids alerts for short blips such as a quick reboot.
- Under Notification Methods, turn on Email Notifications and/or SMS.
The same page has General Alerts for account events, such as invitations and invoice notices.
Track alerts: Alerts
Section titled “Track alerts: Alerts”The Alerts page (/dashboard/alerts, heading Device Alerts) lists
offline alerts. Filter with All Active, Active, Escalated or
Resolved.
| Column | Meaning |
|---|---|
| Device | The router that went offline. |
| Status | Active, Escalated or Resolved. |
| Detected At | When ISPMan noticed it was offline. |
| Duration | How long it has been (or was) down. |
| Notifications | Icons show whether an email, SMS and in-app notification were sent. |
| Resolved By | Automatic when the router came back, or Manual. |
Open an alert to see its Downtime Duration and history. Alerts resolve on their own when the device comes back. If you know a router is gone for good (for example you’ve moved it), click Resolve Alert Manually, add optional Resolution Notes, and click Resolve Alert.
Telemetry alerts
Section titled “Telemetry alerts”For routers with telemetry on, the Telemetry page lists active metric alerts at the top, showing the observed value against its threshold and how long it’s been happening. Subscribed members are notified through the channels in their alert settings. See The MikroTik device page.
Configuration audit issues
Section titled “Configuration audit issues”Configuration problems aren’t outages, so they don’t show as offline alerts. They appear on the router’s Configuration Audit card and in the Config Audit column on All Devices. See The MikroTik device page.