Checkmk 2.3.0

Unraid plugin that installs the Checkmk agent to monitor local services and report issues to a Checkmk server.

  • Network Services
  • Plugins
  • Tools & Utilities
Unraid plugin that installs the Checkmk agent to monitor local services and report issues to a Checkmk server. Version 2.3.0 is approaching end-of-life (29.10.2026); use the 2.5.0 plugin for new installations.

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.

61/100 Good

Maintained
100last commit 19 days ago
Popular
2823 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

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

GitHub stars
23
Open issues
3
Last commit
2026-11-02
Latest release
2026.11.02.25
Activity
rising

Checked 17 days ago - source: GitHub (Donimax/Unraid-check-mk-agent)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Fill in your API address and logins Before running the sample scripts, replace HOST_NAME, SITE_NAME, USERNAME, and PASSWORD with your Checkmk server address, site name, and automation account login. If you leave the example values, the scripts cannot sign in and host creation fails. source
  • Name each host and choose a folder When creating a host through the API, include a host_name and a folder path such as /. Checkmk will reject the request if either is missing, so the new host never appears in your setup. source
  • Pick the right web address type Set PROTO to https when your Checkmk site uses a secure web connection, and http only for a simple local test. The wrong protocol can stop the script from reaching the server at all. source
  • Checkmk Docker and SMART monitoring To monitor the Docker daemon and SMART disk data, follow the Checkmk Docker and SMART plugin instructions linked in the repository README. source
  • Before installing: 2.3.0 end-of-life Checkmk 2.3.0 reaches end-of-life on 29.10.2026. For new installations, use the 2.5.0 plugin instead. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Is the Checkmk 2.3.0 Unraid agent still suitable for a new installation?

The README lists 2.3.0 as EOL 29.10.2026 and 2.5.0 as CURRENT. Use the 2.5.0 plugin for a new installation.

How can I supply the Checkmk agent file for a local Unraid Docker build?

Put the agent file in the check_mk_agent directory, or set CHECK_MK_URL to your Checkmk server URL and site path so the container downloads the agent package.

How can I automatically install the Checkmk Docker and SMART plugins on Unraid?

Create a script scheduled to run at array startup that waits for the Checkmk server, then downloads mk_docker.py and smart into /usr/lib/check_mk_agent/plugins.

What Checkmk API script details can prevent host creation?

Replace the placeholder server address, site name, and automation account login, and include a host name and folder path such as /. Checkmk rejects the request if the host name or folder is missing, and the wrong protocol can stop the script from reaching the server.

Answers sourced from docs.checkmk.com, github.com

Community

Collected 48 days ago - public community threads