# Quantum Scalar i3 SNMP Monitoring Community MKP for monitoring **Quantum Scalar i3** tape libraries with Checkmk. This package adds native-style SNMP checks for devices using the Quantum Scalar i3 / i6 MIB branch: `1.3.6.1.4.1.3697.1.10.15` It is intended for Scalar i3 systems, not for the existing Checkmk `quantum_libsmall_*` checks, which are designed for Quantum Small Tape Libraries. ## What you get - Overall Scalar i3 health status - Library control, drive and media RAS health - Robotics and magazine state - I/E area state - Open RAS ticket count - Tape drive discovery, one service per physical drive - Logical library / partition discovery - Power supply discovery and power consumption - Temperature and humidity sensor monitoring - Capacity monitoring for storage slots, I/E slots, media and cleaning media - HW/SW inventory for Scalar i3 model, firmware, serial numbers and components ## Created services The package can create services such as: - `Quantum Scalar i3 health` - `Quantum Scalar i3 I/E area` - `Quantum Scalar i3 RAS tickets` - `Quantum Scalar i3 capacity` - `Quantum Scalar i3 drive serial-number` - `Quantum Scalar i3 logical library name` - `Quantum Scalar i3 power supply location` - `Quantum Scalar i3 sensor name` The exact number of services depends on the hardware configuration and the data exposed by the device SNMP walk. ## Requirements - Checkmk 2.5 - SNMP access to the Quantum Scalar i3 - Device must expose the Quantum Scalar i3 MIB branch under `1.3.6.1.4.1.3697.1.10.15` ## Installation Install via mkp add / mkp enable, or Setup >> Extension packages.

# KubeVirt Special Agent Community MKP for monitoring **KubeVirt** virtual machines and platform health with Checkmk. This package adds a Checkmk special agent that collects data from the Kubernetes/KubeVirt API and Prometheus metrics. It discovers KubeVirt virtual machines as piggyback hosts and creates VM-level services for CPU, memory, disks, network interfaces, placement and resource information. It is intended for generic KubeVirt environments. For Harvester / SUSE Virtualization platform, Longhorn and node monitoring, use the separate `checkmk-harvester` extension. ## What you get - KubeVirt VM discovery as Checkmk piggyback hosts - VM CPU monitoring - VM memory monitoring - VM disk monitoring - VM network monitoring - VM interface information - VM placement information - VM resource/request information - VM info and lifecycle state - KubeVirt platform health checks on the source host - KubeVirt component health - KubeVirt version information - KubeVirt controller status - KubeVirt migrations - KubeVirt VMI phase summary - KubeVirt workqueue monitoring ## Created services The package can create VM services such as: - `VM CPU` - `VM memory` - `VM disk disk-0` - `VM network default` - `VM interfaces` - `VM placement` - `VM resources` - `VM info` On the source host, it can create services such as: - `KubeVirt component health` - `KubeVirt controller status` - `KubeVirt migrations` - `KubeVirt version` - `KubeVirt VM lifecycle` - `KubeVirt VMI phases` - `KubeVirt workqueues` The exact number of services depends on the number of VMs, VM disks, VM networks and metrics exposed by the monitored KubeVirt environment. ## Requirements - Checkmk 2.5 - Kubernetes API access - Read access to KubeVirt resources - Access to a Prometheus endpoint exposing KubeVirt metrics - A Kubernetes service account / bearer token for the special agent ## Installation Install via `mkp add` / `mkp enable`, or use **Setup > Extension packages**. After installation, configure the **KubeVirt** special agent rule with: - Kubernetes API endpoint - Bearer token from the Checkmk password store - Prometheus endpoint - Cluster name - Optional TLS certificate verification settings A minimal Kubernetes RBAC example is included in the repository under `docs/kubevirt_rbac.yaml`. ## Notes This extension monitors KubeVirt from the platform side. It does not replace guest operating system monitoring inside the virtual machines. For guest OS metrics such as filesystems, processes, services or package inventory, install the normal Checkmk agent inside the VM.

# Harvester Special Agent Community MKP for monitoring **Harvester** and Harvester-based SUSE Virtualization environments with Checkmk. This package adds a Checkmk special agent for Harvester platform, Longhorn storage and Harvester node monitoring. It collects data from the Kubernetes API, Harvester custom resources, Longhorn custom resources, Prometheus metrics and, optionally, a node-local DaemonSet collector. It is intended for Harvester platform monitoring. For KubeVirt VM monitoring, install and configure the separate `checkmk-kubevirt` extension in addition. ## What you get - Harvester version and settings monitoring - Harvester backup target status - Harvester VM image import status - Harvester platform pod summary - Harvester node information and conditions - Harvester node configuration monitoring - Harvester block device discovery - Longhorn node status - Longhorn disk status and usage - Longhorn volume robustness and attachment status - Longhorn replica summary - Prometheus connection health - Optional node-local OS context through a DaemonSet collector - SUSE Linux Micro / SLES identity labels on Harvester node hosts - Native Checkmk node services for filesystems, CPU load, memory, uptime, interfaces, disk I/O and process discovery when node collector output is enabled ## Created services The package can create source-host services such as: - `Harvester Prometheus connection` - `Harvester version` - `Harvester settings` - `Harvester backup target default` - `Harvester platform pods` - `Harvester VM image namespace/name` - `Longhorn replicas` - `Longhorn volumes summary` - `Longhorn volume name` On Harvester node piggyback hosts, it can create services such as: - `Harvester node info` - `Harvester node conditions` - `Harvester node configuration` - `Harvester block device /dev/...` - `Longhorn node status` - `Longhorn disk status disk-name` - `Longhorn disk usage disk-name` - `Harvester node local OS context` - `Harvester node local mounts` - `Harvester node local processes` - `Filesystem /...` - `CPU load` - `Memory` - `Uptime` - `Disk IO SUMMARY` - `Interface ...` The exact number of services depends on the Harvester cluster, Longhorn volumes, node count, mounted filesystems and enabled collection options. ## Requirements - Checkmk 2.5 - Harvester cluster API access - Kubernetes service account / bearer token - Read access to Harvester and Longhorn resources - Access to a Prometheus endpoint exposing Kubernetes, Harvester, Longhorn and node metrics - Optional: node collector DaemonSet from `docs/harvester_node_collector.yaml` ## Installation Install via `mkp add` / `mkp enable`, or use **Setup > Extension packages**. After installation, configure the **Harvester** special agent rule with: - Kubernetes API endpoint - Bearer token from the Checkmk password store - Prometheus endpoint - Cluster name - Node piggyback hostname mode - Optional node collector settings A minimal Kubernetes RBAC example is included in the repository under `docs/harvester_rbac.yaml`. The optional node collector manifest is included under `docs/harvester_node_collector.yaml`. Deploy it only if you want Checkmk to receive node-local context such as OS release details, selected mounts, selected kernel modules and process data. ## Notes This extension focuses on Harvester platform, Longhorn and Harvester node monitoring. For VM-level KubeVirt monitoring, use the separate `checkmk-kubevirt` package.

# 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.

# 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.

# Microsoft Azure Log Analytics Queries for Checkmk Community MKP for monitoring data in **Azure Log Analytics workspaces** with Checkmk 2.5. A special agent runs read-only KQL queries through the Azure Monitor Logs Query API and turns results into Checkmk services. ## What you get - Built-in workspace operations and collector health checks - Custom KQL profiles with configurable WARN and CRIT levels - Shared profiles or profiles assigned to individual workspaces - Multiple workspaces in one rule, with optional readable labels - Alerts when an expected service is missing from a successful query The package can monitor VM, application, and Azure service telemetry **once that data is being sent to a workspace**. KQL examples for App Service, Key Vault, Azure Activity, and messaging are included in the repository. ## Requirements - Checkmk 2.5 - Entra app registration with a client secret and read access to each workspace - Workspace ID GUIDs and outbound HTTPS to Microsoft identity and Azure Monitor Logs endpoints - Data already ingested through AMA/data collection rules or diagnostic settings No additional Python packages, PowerShell modules, Azure CLI, or Azure SDK are required on the Checkmk site. ## Installation Install the MKP, then configure **Azure Log Analytics Queries** under **Setup → Agents → Other integrations**. Store the client secret in the Checkmk password store, add your workspaces and KQL profiles, and discover services. Source and documentation: [https://github.com/ghatak-x/checkmk-azure-loganalytics](https://github.com/ghatak-x/checkmk-azure-loganalytics)