Wheelhouse docs

Monitoring#

Six jobs. Five of them are about getting state off the router, because that is where monitoring belongs.

GuideThe job
Scrape the agentPrometheus metrics: what is exported, and when a series is absent
Ship logs off the boxsystem syslog remote for the journal, and audit_syslog for the audit log
SNMPRead-only communities for a monitoring system that speaks SNMP
Export flows to a collectorNetFlow and IPFIX, so somebody else keeps the history
See what the switch says it isLLDP, and what it settles in thirty seconds
Find what is using the link right nowLive connections, the busiest devices, and their traffic history

What the router keeps, and for how long#

The audit log is the exception to the first half: it is persisted on the box, in /config/wheelhouse/audit.jsonl, and survives a reboot. It is not an exception to the second. Every entry carries a sequence number and the hash of the one before it, and the agent will copy each one to a syslog collector as it is written — off by default, switched on in the agent's own settings, and the third step of Ship logs off the box. Do switch it on: root on the router can rewrite that file, and the copy that proves it is the one that already left. See Harden a router that faces the internet.

The three log-shaped things, which are not the same#

Keeping these apart saves an hour every time something goes wrong.

NameIsWhere
The journalsystemd's log, everything the router's daemons sayLogs
The commit historyNumbered configuration revisions, with a diff per revisionSystem — history
The audit logWho changed what through the agent, from where, with which roleSystem — audit

Updated 2026-09-18 monitoring prometheus syslog netflow