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 ghatak-x
# Microsoft Entra Cloud Sync Monitoring Community MKP for monitoring **Microsoft Entra Cloud Sync** with Checkmk. The package provides a special agent that uses the Microsoft Graph API to monitor Cloud Sync job health and provisioning activity. ## What you get - Cloud Sync job and schedule state - Execution status, freshness and duration - Successive failures and quarantine detection - Synchronized object counts - Provisioning failures and warnings - Automatic recovery handling for resolved provisioning errors - Dropped/deprovisioned object monitoring - Property synchronization activity - Configurable thresholds through Checkmk rules - Optional Windows local checks for Cloud Sync agent version and connectivity ## Requirements - Checkmk 2.5 - Microsoft Entra application registration - Microsoft Graph application permissions: - `Synchronization.Read.All` - `AuditLog.Read.All` - `Directory.Read.All` - Outbound HTTPS access from the Checkmk server to Microsoft Graph and Microsoft identity endpoints No additional Python packages or PowerShell modules are required. ## Installation Install the MKP using `mkp add` / `mkp enable`, or via **Setup > Extension packages**. After installation, configure the special-agent rule: `Microsoft Entra Cloud Sync` Credentials can be stored in the Checkmk password store. The optional Windows local checks can be deployed on the server running the Microsoft Entra Cloud Sync provisioning agent.
by zartion
telegram\_graphs: notificaciones de Telegram con gráficos (Checkmk 2.4.0 Community/Raw) Envía las notificaciones de Checkmk a un chat, grupo o canal de Telegram y adjunta, como álbum en respuesta al mensaje, los gráficos de rendimiento de las últimas 25 h del host o servicio notificado. También puede añadir los gráficos de otros servicios del mismo host (por ejemplo CPU, memoria o interfaces) cuando cae un host. Está basado en telegram\_notify 1.4.3 (el telegram.py del proyecto anterior) y portado a la API de Checkmk 2.4. INSTALACIÓN como usuario del sitio (OMD\[mysite\]:\~$) mkp add telegram\_graphs-2.0.0.mkp mkp enable telegram\_graphs 2.0.0 omd restart apache # para que la GUI cargue el nuevo ruleset En la edición Community también puede hacerse con Setup > Maintenance > Extension packages > Upload package. Se instalan dos ficheros: \~/local/share/check\_mk/notifications/telegram\_graphs → Script de notificación \~/local/lib/python3/cmk\_addons/plugins/telegram\_graphs/rulesets/telegram\_graphs.py → Parámetros en la GUI (Rulesets API cmk.rulesets.v1) CONFIGURACIÓN Cree un bot con @BotFather y guarde el token. Lo ideal es guardarlo en Setup > General > Passwords. Añada el bot al grupo o canal y obtenga el chat ID (en grupos es un número negativo, como -1001234567890). En Setup > Events > Notifications, cree una regla o Notification parameter con el método Telegram (con gráficos). Parámetros disponibles: Token del bot: Obligatorio. Puede ser explícito o venir del almacén de contraseñas. ID del chat: Si se deja vacío, se usa el atributo de usuario TELEGRAM\_CHAT\_ID del contacto, igual que en el plugin anterior. ID del tema: Para supergrupos con temas (message\_thread\_id). Envío silencioso: El texto llega sin sonido. Los gráficos llegan siempre en silencio. URL prefix: Activa los enlaces $LINKEDHOSTNAME$, $LINKEDSERVICEDESC$ y $GRAPH\_URL$. Plantillas host/servicio: HTML de Telegram con macros de Checkmk, con la misma plantilla por defecto que el plugin anterior. Enviar gráficos: Activado por defecto. Estados con gráficos: Por separado para servicios (OK/WARN/CRIT/UNKNOWN) y hosts (UP/DOWN/UNREACHABLE). Máximo de gráficos: 10 por defecto. Si son más de 10 se envían varios álbumes. Servicios adicionales: Expresiones regulares (CPU, Memory, Interface .\*...) de servicios del mismo host con métricas. Se buscan por Livestatus. Adjuntar servicios adicionales en: Notificaciones de host (por defecto), de servicio o ambas. Proxy: Proxy HTTP para llegar a api.telegram.org. CÓMO OBTIENE LOS GRÁFICOS El script usa cmk.notification\_plugins.utils.render\_cmk\_graphs, el mismo mecanismo que el correo HTML de Checkmk. Llama a "http://localhost://check\_mk/ajax\_graph\_images.py" autenticándose con el site internal secret, que es obligatorio desde la 2.3. No hay que crear usuarios de automatización. Checkmk fija el rango de los gráficos en 25 h para las notificaciones. DIFERENCIAS CON telegram\_notify 1.4.3 La GUI usa la Rulesets API de 2.4. La antigua cmk.gui.plugins.wato / notification\_parameter\_registry ya no existe en 2.4. Ya no depende de cmk.utils.site ni de mail.event\_templates, que también desaparecieron en 2.4. Las peticiones de gráficos van autenticadas, porque sin token ajax\_graph\_images.py responde vacío o con error. Primero se envía el texto, que es el que suena, y los gráficos van después como respuesta. Si fallan los gráficos, la notificación no se reintenta, así el texto no llega duplicado. Los códigos de salida siguen la convención de Checkmk: 0 enviado, 1 reintentar (429/5xx/red), 2 error definitivo. Las salidas del plugin se escapan (\, &) para que Telegram no rechace el mensaje con un 400. Es un paquete nuevo (telegram\_graphs) que convive con el anterior. Las reglas antiguas de telegram.py no se migran. DIAGNÓSTICO Log: \~/var/log/notify.log. Suba el nivel en Global settings > Notifications > Notification log level. Para probarlo, use Test notifications en Setup > Events > Notifications, o pulse Send custom notification en un servicio con gráficos.
by MaKaNu
# CheckMK Linux FlexLM Plugin Monitors FlexLM license feature usage and reports the number of licenses in use and their total, along with license expiry dates. ## Prerequisites on the license server - A Linux FlexLM license server with `lmutil` installed. - The path to lmutil will either be determined by systemd service or via PATH variable. - The Checkmk Linux agent must be able to run `lmutil lmstat -a` and `lmutil lmstat -i`. - Checkmk 2.5.0p6 or newer. ## Installation of the MKP Login into your site and provide the mkp file (for example via scp). ```bash mkp add cmk_linux_flexlm-1.0.1.mkp mkp enable cmk_linux_flexlm ``` Copy the agent based plugin to the monitored flexlm server. - Location on site: - `local/share/check_mk/agents/plugins/cmk_linux_flexlm.py` - Target location on flexlm server: - `/usr/lib/check_mk_agent/plugins/cmk_linux_flexlm.py` Run service discovery and accept the deteced services, one for each feature. Create Service rules and apply them via service label to different amounts of feature licesnes.
by ghatak-x
# Microsoft 365 Platform Monitoring Community MKP for monitoring **Microsoft 365** with Checkmk. This package provides three independently configurable special agents for Microsoft 365 monitoring: - Microsoft Graph for service health, incidents, licensing, usage reports and Teams call quality - Exchange Online PowerShell for Exchange Online configuration and drift monitoring - PnP.PowerShell for SharePoint Online tenant and site configuration drift monitoring The integrations use Entra ID app-only authentication. Exchange Online and SharePoint Online use certificate-based authentication. ## What you get - Microsoft 365 service health and active issue monitoring - Microsoft 365 licensing and subscription monitoring - Microsoft 365 usage and activity reports - Teams activity, device usage and call-quality monitoring - Exchange Online organization and transport configuration monitoring - Optional Exchange mailbox, user, role, policy and device configuration monitoring - SharePoint Online tenant and site configuration monitoring - Configuration-drift detection for Exchange Online and SharePoint Online - Configurable WARN/CRIT states and thresholds through Checkmk rules - High-cardinality checks such as per-user, per-mailbox and per-site monitoring can be enabled selectively. ## Requirements - Checkmk 2.5 - Microsoft Entra application registration with the required permissions - Network access from the Checkmk server to Microsoft 365 APIs - PowerShell 7.6\+ for Exchange Online and SharePoint Online monitoring - `ExchangeOnlineManagement` PowerShell module for Exchange Online - `PnP.PowerShell` module for SharePoint Online - Password-protected PFX certificate for certificate-based authentication The PowerShell modules can be installed directly as the Checkmk OMD site user with `-Scope CurrentUser`. Microsoft Graph monitoring does not require PowerShell modules. ## Installation Install the MKP using `mkp add` / `mkp enable`, or via **Setup > Extension packages**. After installation, configure one or more of the following special-agent rules: - `Microsoft 365 via Microsoft Graph` - `Microsoft 365 Exchange Online via PowerShell` - `Microsoft 365 SharePoint Online via PnP PowerShell` Secrets and PFX passwords can be stored in the Checkmk password store.
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).
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.