jmrplens/mikroscope-agent repository overview

⁠mikroscope-agent

Sub-second, kernel-level telemetry agent for container-capable MikroTik RouterOS devices. One static Go binary in a scratch image, nothing else: it runs on the router and reads the shared kernel's /proc at 10 Hz (per-core CPU with the softirq split, softnet drops, interrupt affinity), where every existing exporter is stuck at the 1 s cpu-load the RouterOS API reports.

This is the image the router pulls. Docker Hub is where a RouterOS device looks by default (/container/config registry-url ships pointing at registry-1.docker.io), so the install needs no upload and no architecture choice:

mikroscope install --router [email protected] --remote-image jmrplens/mikroscope-agent:latest

Pin the version instead of latest for a deployment you want to be able to reproduce. The same image is published at ghcr.io/jmrplens/mikroscope-agent.

⁠Platforms

linux/amd64, linux/arm64, linux/arm/v7, linux/arm/v5.

⁠Requirements

RouterOS 7.24 or later with device-mode container=yes, which MikroTik gates behind a physical reset-button press or a power cycle. mikroscope doctor --router … checks every prerequisite against your own device and names the fix for anything missing.

⁠Reading it

The agent answers plain HTTP on the container's veth. The mikroscope CLI (or the jmrplens/mikroscope collector image) records a window with markers, draws the chart, or forwards the stream into Prometheus, InfluxDB 3, Loki, OTLP, Graphite, Elasticsearch, PostgreSQL, Telegraf and the file.

⁠Links

• Source: https://github.com/jmrplens/mikroscope⁠
• Documentation: https://jmrp.io/docs/mikroscope/⁠
• Install routes: https://jmrp.io/docs/mikroscope/install/routes/⁠
• Prerequisites: https://jmrp.io/docs/mikroscope/install/prerequisites/⁠
• Collector image: https://hub.docker.com/r/jmrplens/mikroscope⁠

MIT license. By José M. Requena Plens, https://jmrp.io/⁠.