Extend your Checkmk monitoring with packages created by community members. Or create your own packages and share the here with the rest of the community.
by mape2k
This agent plugin for Gentoo based hosts checks pending updates and unpatched security advisories.
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)
Docker reports the CPU usage of a container like `docker stats`: **100 % per fully used CPU core**. On a host with many cores a single container can show hundreds or thousands of percent, which breaks every threshold written for "total CPU in %". On Checkmk versions older than 2.5.0p12 the built-in service also shows a bogus "under high load for ... years" duration (Werk 20187). This package adds the service **Docker CPU utilization** for Docker container hosts. It reports the utilization in percent of the available CPUs (always 0 to 100 %) and the number of CPU cores in use. ## Features - Normalized CPU utilization per container, e.g. `Total CPU: 1.48%, 1.07 of 72 CPUs in use` - Metrics `util` (shown in the standard CPU graph) and `docker_cpu_cores_used` - Levels in the WebUI, with levels over an extended time period as default (WARN after 1 h 30 min, CRIT after 3 h at 90 %), so short peaks do not alarm - Works with the **standard Docker data** of `mk_docker.py`, no agent plug-in has to be rolled out - Optional agent plug-in for **Linux and Windows** (Agent Bakery rule) that also reports the container CPU limit - Counter resets after a container restart are ignored instead of producing negative values - The built-in "CPU utilization" service is not changed - Safe to install: no service is created until a discovery rule exists ## Requirements - Checkmk **2\.5.0 or newer** - Docker hosts monitored with the Docker agent plug-in `mk_docker.py` (container hosts as piggyback hosts) ## Notes - With the standard Docker data the CPU limit of a container is not known, the value is related to all CPUs of the Docker host. The optional agent plug-in also takes the limit into account. - Full documentation and changelog are included in the package (`doc` folder, in English). ## Tested Tested live on Checkmk 2.5.0p10 in a distributed setup with the standard Docker data on Linux Docker hosts. The optional agent plug-in was checked on a Linux Docker host up to the delivery of its data. The Windows variant has not been tested on a real Windows Docker host. --- ## Deutsch Docker meldet die CPU-Nutzung eines Containers wie `docker stats`: **100 % pro voll ausgelastetem CPU-Kern**. Auf einem Host mit vielen Kernen kann ein einzelner Container hunderte oder tausende Prozent zeigen, wodurch alle Schwellwerte für "Gesamt-CPU in %" nicht mehr funktionieren. Bei Checkmk-Versionen vor 2.5.0p12 zeigt der eingebaute Service außerdem eine falsche Dauer "under high load for ... years" (Werk 20187). Dieses Paket fügt den Service **Docker CPU utilization** für Docker-Container-Hosts hinzu. Er zeigt die Auslastung in Prozent der verfügbaren CPUs (immer 0 bis 100 %) und die Zahl der genutzten CPU-Kerne. ### Funktionen - Normalisierte CPU-Auslastung pro Container, z. B. `Total CPU: 1.48%, 1.07 of 72 CPUs in use` - Metriken `util` (im Standard-CPU-Graphen sichtbar) und `docker_cpu_cores_used` - Schwellwerte in der WebUI, standardmäßig über einen Zeitraum (WARN nach 1 h 30 min, CRIT nach 3 h bei 90 %), kurze Lastspitzen alarmieren nicht - Arbeitet mit den **Standard-Docker-Daten** von `mk_docker.py`, es muss kein Agent-Plugin ausgerollt werden - Optionales Agent-Plugin für **Linux und Windows** (Agent-Bakery-Regel), das auch das CPU-Limit des Containers meldet - Zählerrücksetzungen nach einem Container-Neustart werden ignoriert, statt negative Werte zu erzeugen - Der eingebaute Service "CPU utilization" wird nicht verändert - Sicher zu installieren: Ohne Discovery-Regel wird kein Service angelegt ### Voraussetzungen - Checkmk **2\.5.0 oder neuer** - Docker-Hosts, die mit dem Docker-Agent-Plugin `mk_docker.py` überwacht werden (Container-Hosts als Piggyback-Hosts) ### Hinweise - Bei den Standard-Docker-Daten ist das CPU-Limit eines Containers nicht bekannt, der Wert bezieht sich auf alle CPUs des Docker-Hosts. Das optionale Agent-Plugin berücksichtigt auch das Limit. - Die vollständige Dokumentation und das Changelog sind im Paket enthalten (Ordner `doc`, auf Englisch). ### Getestet Live getestet auf Checkmk 2.5.0p10 in einer verteilten Umgebung mit den Standard-Docker-Daten auf Linux-Docker-Hosts. Das optionale Agent-Plugin wurde auf einem Linux-Docker-Host bis zur Lieferung seiner Daten geprüft. Die Windows-Variante wurde auf keinem echten Windows-Docker-Host getestet.
by Django01
# Apprise Notifications for Checkmk Send Checkmk host and service notifications to an **Apprise API server** and let Apprise handle the final routing to your notification services. This extension adds a native **Apprise** notification method to Checkmk Setup. Checkmk sends a provider-independent notification to Apprise, while destinations such as Signal, Matrix, Discord, Slack, Gotify, email and other services remain configured centrally in Apprise. ## Features - Native Checkmk notification method and Setup form - Checkmk 2.5.x - Host and service notifications - Problem and recovery notifications - Acknowledgements - Downtime start, end and cancellation - Flapping and custom notifications - Apprise tag-based routing - HTTP Basic authentication - Checkmk Password Store support - Plain text and rich-text messages - TLS certificate verification enabled by default - Optional private CA certificate - Configurable request timeout - Checkmk-native retry behavior for temporary delivery failures - No Apprise package or additional Python dependencies required on the Checkmk server ## Requirements - Checkmk 2.5.x - Apprise API with Apprise 2.0 or newer - A saved Apprise configuration reachable from the Checkmk site The extension uses the stateful Apprise API endpoint: `POST /notify/{config_id}` Provider configuration stays entirely on the Apprise side. ## Routing A Checkmk notification rule can optionally pass an Apprise tag expression. For example: - `ops` - `network` - `ops night` - `ops, oncall` This makes it possible to use Checkmk rules for deciding **when** a notification is generated while Apprise decides **where** it is delivered. ## Security - TLS verification is enabled by default. - Private CA certificates are supported and must reside inside the Checkmk site directory. - Credentials can be stored in the Checkmk Password Store. - Credentials, server URL, configuration ID and response bodies are not written to notification output. - Redirects and environment proxies are intentionally not used. ## Compatibility Verified with: - Checkmk 2.5.x - Checkmk Community Edition - Checkmk Enterprise Edition - Python 3.13 on the Checkmk site - Apprise 2.0 - End-to-end delivery through Apprise to Signal The MKP declares compatibility with Checkmk 2.5.x only. ## Installation Install the MKP and enable it, then create a notification rule using the **Apprise** notification method. No additional Python modules are required on the Checkmk server. Full installation, configuration and troubleshooting documentation is available in the project repository: [https://github.com/Django1982/CheckMK\_Apprise\_MKP](https://github.com/Django1982/CheckMK_Apprise_MKP) ## License GPL-2.0-only
by avaccaro
A Checkmk agent plugin that discovers host capabilities and reports each one as a host label, so you can see at a glance which plugins are worth installing on that host. From the Capability Scout service's detail you can then add the bakery rules to deploy the corresponding plugins or access user guide pages, when available. Coverage today includes databases, web and application servers, containers and virtualization, clustering and HA, backup and DR, messaging and monitoring engines, collaboration platforms, and cloud VM provisioning. **Prerequisites** For the Capabilities Scout service to render correctly, set these two things in Checkmk: 1. Do not escape HTML in service output: add a rule under Setup → Services → Service monitoring rules → "Escape HTML in service output", set it to "Don't escape HTML", limit it to the Capabilities Scout service, and activate changes. Without it, the logos and "Add rule" links show up as raw HTML text. 2. Increase maximum long output size: on hosts with many capabilities, raise Setup → Global settings → "Maximum long output size" above its default of 2000 bytes. Otherwise the service details are cut off.
by rsander
Agent Plugin to check SSL certificates in specified directories Now with support to check signature algorithm Windows Plugin added JSON data in agent data section Is now able to ignore certificates with a short lifetime
by simonmeggle
Robotmk integrates Robot Framework results into Checkmk.
by lgbff
This check monitors the status of ssl cert checks on ssllab.com. Changelog: - 3\.2.0 no systemtime in agent output - 3\.x version for cmk 2.2 - 2\.1.0 change to python3 - 2\.0.1 fix datasource\_programm group definition - 2\.0.0 insert cache for api response - 1\.6.0 insert Agent status (line\[3\]) - 1\.5.3 change default status - 1\.5.2 Insert Agent Header infos - 1\.5.1 cache default settings - 1\.5.0 new data seperator (59) - 1\.4.9 fix display JSON Error on check result. - 1\.4.8 fix connect exeption - 1\.4.7 add default value for timeout - 1\.4.6 change timeout handling - 1\.4.5 fix inventory issue while JSON issues - 1\.4.4 change urlopen error handling - 1\.4.3 Rename check file - 1\.4.2 Fix check manpage - 1\.4.1 delete modul calls from check - 1\.4.0 changes for cmk version 1.4 - 1\.3.1 improve error handling.
by rsander
Plugin to gather Ceph statistics. ### Starting with Checkmk 2.4, this plug-in is distributed with Checkmk. No need to download this MKP. Use this MKP only if you want to monitor Ceph with Checkmk 2.2 or 2.3.