PatchMon-exporter
Prometheus exporter for PatchMon that answers "is the fleet actually patched?" - a different question from "is PatchMon up" or "did the agent check in", both…
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.
44/100 Fair
- Maintained
- 69last commit 65 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 502 GB minimum RAM
Availability: platform listings confirmed today, links checked 24 days ago
- GitHub stars
- 1
- Open issues
- 0
- Last commit
- 2026-09-17
- Activity
- stale
Checked 8 days ago - source: GitHub (louij2/patchmon-exporter)
Resources & Compatibility
Minimum requirements: 2 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Run the Docker quick start Create a `patchmon` folder, run the setup script, then run `docker compose up -d`. This creates your settings and passwords, starts the app, and lets you open `http://localhost:3000` to create your admin account and add hosts. source
- Fill in the three secrets If you do the manual setup, copy `env.example` to `.env` and set `POSTGRES_PASSWORD`, `REDIS_PASSWORD`, and `JWT_SECRET` to long random values. These protect your database and logins; if they are missing or too weak, the app may not start or you risk unsafe access. source
- Open port 3000 for the web UI Allow access to port 3000 if you need to reach the dashboard from another device. That is the web UI port, so if it is blocked you cannot sign in, add hosts, or see patching status. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does patchmon-exporter need a PatchMon API key to read host patch state?
No. It reads PatchMon's Postgres backing store directly, because PatchMon's REST API needs a session or API key per host and does not provide a fleet-wide read token.
How should the exporter receive its database connection string?
Put a standard Postgres connection string in a DSN file, by default /run/secrets/patchmon-dsn, and override the path with PATCHMON_DSN_FILE if needed. Do not bake the DSN into the image or pass it as a plain environment variable.
What port does patchmon-exporter expose and what path should Prometheus scrape?
It listens on port 9820 by default, which can be changed with LISTEN_PORT. Prometheus should scrape the /metrics path on that port.
What network access does the exporter need to work?
It needs network access to PatchMon's Postgres instance. You can join the same internal Docker network as PatchMon or expose the database port to the exporter.
Which metric shows whether hosts are actually patched rather than merely checking in?
Use patchmon_host_patch_stale_seconds, which measures the age since a host last successfully applied updates. It is independent of whether the agent is still checking in on schedule.
Answers sourced from github.com
Community
Collected 48 days ago - public community threads