Monitor Agent

Monitor Agent is a lightweight host-metrics agent that pushes CPU, memory, network, array-disk, ZFS-pool, and Docker-container statistics to your Monitor…

  • Monitoring & Logging
  • Network Services
  • Tools & Utilities
Monitor Agent is a lightweight host-metrics agent that pushes CPU, memory, network, array-disk, ZFS-pool, and Docker-container statistics to your Monitor dashboard. Built for Unraid servers, it runs with host networking, privileged mode, and host /proc mounts so metrics reflect the whole server, not just the container. An ingest token from your Monitor instance is required for the agent to connect.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

38/100 Low

Maintained
66last commit 159 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 20 days ago

GitHub stars
0
Open issues
2
Last commit
2026-06-15
Latest release
agent/v2.0.32
Activity
stale

Checked 6 days ago - source: GitHub (RealFascinated/Monitor-Agent)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s), 100 GB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create and edit your .env file Copy .env.example to .env and fill in your settings before starting anything. This .env file is where the app reads its keys and options; without it, the monitor may start but not work properly. source
  • Use the setup script, then start Docker Make setup_and_run.sh executable, run it, then run docker compose up to start the app. Docker is the container system that runs the monitor, and this step prepares configs, checks them, and launches it. source
  • Keep config names matching When editing monitors, make sure the network and trigger names match the exact names in the network and trigger files. If a name is missing or misspelled, the monitor won’t start because it can’t find that network or alert. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What credential does the agent need to connect to a Monitor instance?

It requires an ingest token, which can be supplied in config or via the MONITOR_INGEST_TOKEN environment variable.

Does the Windows install need elevated permissions?

Yes, it must run as Administrator so hardware sensors, including GPU power, can be read.

Can I configure the agent without a config.yml file?

Yes, the config file is optional and you can provide all settings through environment variables, which override values from a file.

How do I expose host disks to a containerized agent?

Use MONITOR_HOST_ROOT to specify the host root bind mount prefix used for disk metrics in containers.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads