by turretsec

Monitor **ArcGIS Enterprise** in Checkmk via the ArcGIS REST Admin API. The special agent runs from a Checkmk host representing ArcGIS Portal, collects Portal-level health and configuration, automatically discovers federated ArcGIS Server sites, and emits per-server data as piggyback. ### What it monitors - **Portal** - health, index sync, federation status, license / member usage - **Federated Servers** - auto-discovered; service health, machine state, web adaptors, datastore validation - **Per-service metrics** - request rate, failure & timeout rates, response & wait times, running instances (graphed and perfometer'd) - **Logs** - severe/warning counts and log configuration for Portal and Server - **Collection Status** - a single service summarizing every collection step, so partial API failures are visible instead of silent ### Highlights - Auto-discovery of federated servers - point it at Portal and go - Configurable collection scope, cache intervals, and server include/exclude filters - Per-collection error isolation: one failing endpoint never takes down the whole run - Works with single-server, distributed, and HA deployments ### Requirements - ArcGIS Enterprise **11.1+** - Checkmk **2.3.0p1+** - A Portal admin account; network reach to each federated server's admin URL Full documentation, configuration guide, supported deployment topologies, and an optional dashboard: **https://github.com/turretsec/cmk-arcgis**

by turretsec

Monitor **ArcGIS Enterprise** components for available patches on Windows hosts. The agent plugin runs directly on each ArcGIS host, discovers installed components from the Windows registry, and compares applied patch QFE_IDs against Esri's patch notification feed. One service per component, no manual configuration of what is installed. ### What it monitors - **ArcGIS Server, Portal, and Data Store** - patch status via QFE_ID comparison against Esri's feed - **Security patches** - immediate CRIT on any missing security patch, regardless of thresholds - **Non-critical patches** - configurable WARN when patches are available - **Overdue patches** - configurable CRIT when the oldest unapplied patch exceeds an age threshold ### Highlights - Auto-discovery via Esri's QFEPatchFinder and QFEARP registry markers - no manual component list - QFE prefix auto-detection from applied patches - works for any Esri product without hardcoding - Patch feed cached locally - survives feed outages with stale cache fallback - Configurable feed URL for internal mirrors and air-gapped environments - Agent Bakery deployment with per-host feed and cache configuration - Service monitoring rule for per-host and per-component threshold tuning ### Requirements - ArcGIS Enterprise **11.1+** (may work on earlier versions but untested) - Checkmk **2.3.0p1+** - Windows host with ArcGIS Enterprise components installed Full documentation, installation guide, and community contribution instructions for unverified components: **https://github.com/turretsec/cmk-arcgis-updates**

by turretsec

Monitor **CTDB cluster health** in on active/active Samba/CTDB nodes. An agent plugin runs locally on each node in the CTDB cluster, reading `ctdb status` and `ctdb ip all`, and reports both this node's CTDB-reported health and the cluster's shared state - recovery mode and public IP allocation. ### What it monitors - **Node health** - CTDB-reported state (OK / PARTIALLYONLINE / DISABLED / STOPPED / UNHEALTHY / DISCONNECTED / BANNED), distinct from whether ctdbd is merely running - **Recovery mode** - cluster-wide NORMAL vs RECOVERY, with a grace period so a normal brief failover doesn't alert while a stuck recovery does - **Public IP allocation** - orphaned IPs with no owning node, and uneven distribution across the cluster - **Recovery duration** - graphed metric for spotting recoveries trending longer over time ### Highlights - Reads local CTDB state only - Every severity independently configurable per state - Intentional per-node redundancy - each node reports the full cluster picture - Deployed and configured via the Checkmk Agent Bakery ### Requirements - A Linux CTDB cluster with the ctdb CLI installed - Checkmk 2.3.0p1+ - No credentials required Full documentation and configuration guide: https://github.com/turretsec/cmk-ctdb