Packages
  • Checkmk special agent \+ check plugins that monitor a Hermes Agent installation through its web dashboard's public REST API

  • Checkmk MKP that monitors OPNsense firewalls through the OPNsense REST API. Not an replacement for the checkmk agent, but an addition.

  • Checkmk MKP that monitors a Proxmox Mail Gateway (PMG) node through its REST API. Not meant as an replacement for the Linux agent, but as an addition.

  • Checkmk check plugins that monitor the PowerDNS Authoritative Server and the PowerDNS Recursor through their built-in HTTP APIs, with a control-socket fallback (pdns\_control / rec\_control) when the API is unavailable.

  • Checkmk special agent \+ check plugins that monitor a Proxmox Backup Server (PBS) through its REST API. Not meant as a replacement for monitoring via the Checkmk agent, but as an addition.

  • Checkmk MKP that monitors the ZFS Adaptive Replacement Cache (ARC) on a Linux host with ZFS installed.

  • Checkmk special agent that monitors an openWB wallbox controller through its read-only simpleAPI HTTP endpoint. Not meant as a replacement for the Linux agent, but as an addition.

  • Checkmk special-agent plugin that monitors the DNS-based mail security posture of one or more domains, plus a bundled overview dashboard.

  • Checkmk special agent that queries a Home Assistant instance and creates Checkmk piggyback hosts grouped by Home Assistant area/room, with one service per imported entity.

  • Checkmk MKP that monitors the DNSSEC status of arbitrary domains. It runs entirely from the Checkmk site — no agent needs to be deployed on the monitored host, and it has no Python dependencies (pure standard library, no dnspython).

  • Monitors the unbound caching/validating DNS resolver via agent plugin: answer rates by rcode, cache hit ratio/miss rate and unwanted reply rate. Works on Linux and \*BSD (with manual deployment). Replacement for outdated and upsream-removed [https://exchange.checkmk.com/p/unbound](https://exchange.checkmk.com/p/unbound) MKP

  • Finds applications that are running on your hosts but not monitored yet, and suggests the agent plug-in or special agent that would cover them. The Monitoring Coverage Analyzer (MCA) looks at the agent data Checkmk already has and finds applications and subsystems that are running on agent-monitored hosts but not monitored yet (databases, web servers, Hyper-V, SAP, Veeam, Citrix, ...). For each finding it names the agent plug-in or special agent that would cover it, including checks from MKPs installed on your site. - GUI page "Setup > Maintenance > Analyze monitoring coverage" with the coverage of all hosts and open findings per host - One service "Checkmk Monitoring Coverage" per host - Nothing to deploy on your hosts: uses the agent data Checkmk has already cached - Works in distributed setups (analysis on the central site only) - Findings can be ignored with a Setup rule Detection is heuristic by design (curated rules plus a fuzzy search across all check plug-ins of the site), so false positives and false negatives cannot be ruled out completely. Please report them on GitHub. After installing, run once as the site user: mcactl setup Requires Checkmk 2.5.0p15 or later, also runs on 3.0. Developed with the help of AI coding assistants; designed, reviewed and tested on real Checkmk sites by the authors. Source, documentation and issues: [https://github.com/Gulaschcowboy/checkmk\_monitoring\_coverage\_analyzer](https://github.com/Gulaschcowboy/checkmk_monitoring_coverage_analyzer)

  • Citrix Virtual Apps and Desktops (CVAD, formerly XenApp/XenDesktop) monitoring via the on-premises REST API (Citrix Orchestration Service) Drop in replacement for the buildin citrix\_farm.ps1 withlout all it's configuration hassle. Reuses Checkmk's built-in citrix\_state, citrix\_serverload, citrix\_sessions and citrix\_hostsystem.

  • Citrix XenServer and XCP-ng monitoring via the XAPI management API (read-only special agent, no agent on the hypervisors) — pool members and HA, alerts, storage repositories (capacity, I/O, attach state, multipath), plus piggyback data per hypervisor host (CPU, memory, interfaces, license, updates, certificates) and per VM (power state, CPU, memory, disks, NICs, snapshots, guest tools).

  • LinOTP two-factor authentication server monitoring via its API - token counts and per-resolver user counts per realm with configurable levels, storage encryption, config sync, and license & support status including LinOTP's grace-limit message.