Logs

Live and historical packet log viewer

The Logs page is the long-form view of every packet your station handles — the same stream the dashboard skims, but with filters, more rows, and a CSV export. Use it when you’re hunting a specific station, debugging a digipeater rule, or sanity-checking what’s actually going out on the air.

Reading a row

Each row carries a timestamp, packet type, source → destination, channel, distance from your station, and the raw frame on a second line. A small label next to the source tells you where the packet came from:

• (no label) — heard on RF.
• iGate RF→IS — the same packet, after your iGate forwarded it to APRS-IS. The on-the-air copy and the gated copy sit next to each other so you can confirm the gate is actually working.
• iGate IS RX — received from APRS-IS, not heard locally on the air.
• Beacon — transmitted by one of your own beacons.

Controls

• Refresh — pull the latest entries.
• Export CSV — download the current view for offline analysis or to attach to a bug report.
• The type filter at the top narrows the table to a single packet kind (mic-e, position, weather, telemetry, object, status, third-party, message, …).
• Auto-refresh — on by default, the page polls for new packets every couple of seconds. Turn it off to freeze the list so the rows you’re reading stop changing while you study a packet path; the Refresh button still pulls the latest on demand.
• Auto-scroll — on by default, the view follows new packets to the bottom. Turn it off to keep your scroll position put as packets arrive, then use the Jump to bottom control when you want to catch up.
• Non-ASCII data — off by default. Turn it on to surface non-printable bytes in the raw packet line as styled <0x7f> hex tokens, handy when a stray control character (for example a 0x7F wedged into a position report) is breaking map plotting. Left off, the line reads as ordinary text.
• The entry count under the controls shows how many rows you’re looking at. The toggles are remembered per device, so a phone can stay frozen while a desktop keeps tailing.

Logs share the underlying packet ring buffer and WebSocket stream documented on the Monitoring page, so anything you see here is also available over the REST API for scripts, dashboards, or external loggers.