Icinga for Windows – Age of PowerShell
summary
Icinga for Windows fixes the v1.11.0 bug fixes that broke update handling and plain-config writer, adds Hyper‑V checks for duplicate VMs, blackout/migration timing and node counts, and ships a plugin collection with crash fixes. CPU metrics deliberately can exceed 100% to reflect Turbo/Boost behavior. Performance improves with a C Powershell service or a REST API mode that lets the Icinga agent call checks directly (no per‑check PowerShell spawn); this requires Icinga 2.14 requirement on masters/agents and Director 1.11. 2.0 beta targets June 2024.
AI-written summary · about
chapters (11)
- 0:00Introduction to Icinga for Windows
- 4:13Icinga for Windows overview
- 7:29CPU metrics and confusion
- 8:12Architecture and deployment
- 13:06Live demo installation
- 17:28Powershell service and performance
- 19:36Powershell connector improvements
- 23:30Icinga 2.14 integration
- 27:45Just Enough Administration (JEA)
- 32:27Future of Icinga for Windows 2.0
- 42:49Q&A and closing
related talks
46mWhy favour Icinga over
43mWindows Monitoring 3.0 – Now more than ever!
01h 05mCurrent State of Icinga
47mScaling Icinga2 with many heterogeneous projects
42mIcinga2 Automated
47mAsset Management with GLPI and automatically creating the Icinga Config out of GLPI
38mCurrent State of Icinga DB
01h 33mFinding Performance Bottlenecks with PowerShell