Icinga as aggregation tool
summary
Uses Icinga2 as a front layer that ingests events via API connectors from Zabbix, SCOM/Broadcom, Tivoli/CA and others, stores state in Redis, Icinga DB and Postgres, and renders unified views in Icingaweb2 with custom modules. Integrates ticketing (ServiceNow, Jira, Request Tracker) so a single click creates a ticket in the right backend, supports two‑level dependency graphs, and can trigger immediate rechecks back to the source systems. Demo handles ~5k objects instantly and a production case of 2 million objects → 3s load, with the custom layout module slated to be open source.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:46Monitoring tool sprawl problem
- 4:35Single pane of glass solution
- 7:26Front layer architecture
- 13:24Demo and custom dashboards
- 21:32Deployment and future plans
- 21:55Q&A
related talks
29mHow Companies use Icinga
46mWhy favour Icinga over
34mEnhancing Visualization in IcingaWeb2: From Markdown to Metrics
47mAsset Management with GLPI and automatically creating the Icinga Config out of GLPI
01h 06mCurrent State of Icinga
35mMake IT monitoring ready for cloud-native systems
35mData Warehouse Monitoring with Icinga 2
29mAuto Discovery with Icinga