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 TonyBostonTB
MikroTik RouterOS monitoring for CheckMK Monitors MikroTik RouterOS devices via the RouterOS API (v2, port 8729/SSL or 8728) or the RESTful API. Provides checks for: - System health, fans, and temperature sensors - Power supply units (per-PSU voltage, current, and wattage), PoE consumption - BGP and OSPF neighbors - not tested - VRRP status - not tested - IPsec tunnels - not tested - Firewall rules (with optional disabled-rule visibility) - not tested - File age monitoring - RouterOS Info: model, serial number, RouterOS version (with minimum version enforcement) and RouterBOOT firmware (state if an upgrade is pending) - HW/SW inventory: model, serial number, RouterOS version, RouterBOOT firmware - License expiration (CHR) - WiFi per SSID: connected clients, signal strength and radio state, for the new wifi driver, the legacy wireless driver (not tested) and CAPsMAN, new and legacy (one controller covers all its access points) - HW/SW inventory of the access points managed by a CAPsMAN controller: identity, model, serial number, RouterOS version, base MAC Requirements: CheckMK 2.4 or later, RouterOS 7.x. Upgrading from 3.x: stored rules are migrated automatically on install. See "Migration from v3.x" in the README for the power service change. Changes per release are shown in the version description below. Full changelog: [https://github.com/TonyBostonTB/CMK\_Mikrotik/blob/main/CHANGELOG.MD](https://github.com/TonyBostonTB/CMK_Mikrotik/blob/main/CHANGELOG.MD) Issues and source: [https://github.com/TonyBostonTB/CMK\_Mikrotik](https://github.com/TonyBostonTB/CMK_Mikrotik) Based on the original plugin by Andrea Fadda (devilofhell87).
Commvault backup monitoring via the CommServe REST API (special agent) — last backup job per subclient with configurable job states, active jobs with runtime levels and wait reason, storage pool status and capacity (filesystem levels and trends), VM summary and one piggyback service per VM with SLA and protection status, MediaAgent status, license expiry and usage per license type. Beta (0.9.0): incompatible changes are expected before 1.0.0.
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.
by alex23
This Checkmk monitors the memory usage of Extreme Networks switches running VOSS (VSP Operating System / Fabric Engine) via SNMP.
by otAAAh
A guided setup wizard for the Generic JSON API agent — build a monitoring rule from your API's real response, right inside Checkmk. This is the optional companion to the **Generic JSON API** package. It adds an in-site wizard under **Setup → Quick setup** that walks you from a live API response to a finished rule — no `rules.mk`, no `curl`, no leaving Checkmk. ## Requires - The **Generic JSON API** (`json_api`) package must be installed and enabled first — this Explorer only *builds* rules for that agent; it does not monitor anything on its own. - **Checkmk 2.5 or newer**, any edition. The wizard is built on Checkmk's native Quick-Setup UI, which does not exist on 2.4. ## What it does - 🧭 **Guided, step by step** — choose the target folder and host, define one or more endpoints (URL, method, auth, headers, TLS/redirect options), then pick the fields to monitor. - 🔎 **Fetches the real response** — the wizard calls each endpoint from the site and shows you the actual JSON, so you click the fields that exist instead of guessing paths. The call is fully authenticated, OAuth 2.0 included: the wizard performs the token exchange itself, so the preview is exactly what the agent will see. - 🧾 **Body *and* headers** — a tab beside the field picker lists the response headers, so a rate-limit budget or a `Last-Modified` age is one click away instead of a path typed from memory. - 🎯 **Point-and-pick fields** — select values by path, set WARN/CRIT thresholds, units, a numeric transform, an aggregation over a collection, a counter's rate or a timestamp's age, string matching, or turn each element of a `[*]` collection into a Checkmk host of its own — the same options the agent supports. - 🔖 **Names that survive contact with a second endpoint** — an endpoint can put its own name in front of its field service names, so two applications monitored by one rule do not both produce `JSON STATUS`; the endpoint's own status service joins that group as well. The wizard offers it in the connection step and applies Setup's own rule: the prefix needs a name. - 🧩 **One service for several fields** — a field can report into a shared service instead of getting one of its own, so a small API becomes one service whose state is the worst of its fields. The wizard offers it on each field, and the review step previews the result like any other. - 📄 **Keep the response that caused the state** — an endpoint can report its raw body and response headers in its own service details, so the response that made a service CRIT is readable from the service itself instead of from a URL your browser may not even reach. Credentials are masked first. - ✅ **Live preview before you commit** — the review step evaluates every chosen field against the fetched sample and shows the resulting service state, so you catch a wrong path or threshold before the rule exists. - 🔐 **Secure by default** — credentials are stored in the Checkmk password store and referenced, never written in clear text; TLS verification stays on. That covers basic auth, bearer tokens, API keys and OAuth 2.0 client credentials alike. - 🚀 **One click to create** — the wizard writes the finished Generic JSON API rule for you. ## In short Install the **Generic JSON API** agent, then install this Explorer. Open **Setup → Quick setup → Generic JSON API**, point it at an endpoint, tick the fields you care about, and press create. The services appear on your host. ## Details - Extra/companion package — install alongside, and after, the Generic JSON API agent. - Checkmk **2\.5\+**, any edition. - Install via `mkp add` / `mkp enable`, or **Setup → Extension packages**. - GPL-2.0-only.
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.