Logs

The RouterOS event stream, filtered by level and topic and searchable, with a detail view per entry.

Last updated Aug 14, 2026View as Markdown

Overview

The Logs page streams RouterOS events into a filterable table. Three controls sit above it, namely a multi-select for severity Level, a multi-select for Topic built from the topics actually present in the stream, and a free text Search that matches anywhere in the message. Badges below the filters count how many entries fall into each severity.

Clicking a row opens Log details, which shows the full entry field by field. Use it when a message is truncated in the table.

The page is not on the router tab bar. Reach it at /router/<router-id>/logs in the panel.

Before you start

  • The session must hold valid credentials for this router.
  • RouterOS only keeps a limited buffer of log entries; the panel shows what the router still holds.

Steps

  1. Open the logs page for the router.
  2. Narrow by severity with the Level select, which is searchable and accepts several values at once. Leave it empty for All levels.
  3. Narrow by subsystem with the Topic select. Leave it empty for All topics.
  4. Type a keyword into Search. The filter is debounced, so it applies a moment after you stop typing.
  5. Click a row to open Log details, and page through results with the previous and next buttons.
  6. Press Refresh to pull the stream again.

Reference

Levels

info, warning, error, critical, debug.

Log details fields

Field What it shows
Timestamp When RouterOS recorded the entry.
Level Its severity.
Topic The RouterOS topics attached to it.
Message The full message text.
Log ID The entry’s identifier.
Prefix The log prefix, where one is set.
Account The account associated with the entry, where there is one.
Count How many times the entry repeated.

Troubleshooting

The stream is empty after filtering. Clear the Level and Topic selects and the Search box, then narrow again one control at a time.

Nothing loads at all. Press Refresh, and check the router is reachable and the session credentials are valid.