Download as PDF, PPTX
Uploaded byIcinga
Icinga Camp Amsterdam - Icinga Director
Icinga Director is a configuration management tool that allows for easy centralized configuration and deployment of monitoring configurations to Icinga nodes. It supports fully automated environments as well as point-and-click users. The talk demonstrated Icinga Director's installation, architecture, automation capabilities, REST API, and extensibility through modules. Icinga Director aims to make monitoring configuration "just work" across dynamic infrastructures.
More Related Content
Similar to Icinga Camp Amsterdam - Icinga Director
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Icinga Camp Amsterdam - Icinga Director
- 1.
- 2. Thomas Gelf Web 2Product owner Module prototyping machine Principal Consultant @netways
- 3.
- 4. Talk structure while (!$talk->outOfTime()) { $camp->showSomeSlides() ->doFancyLiveDemo(); }
- 6.
- 7. Motivations for anew config tool Icinga 2: new config format DSL old config tools do not fit any more Ever configured a DSL?
- 8.
- 9. Installation provide a database tellDirector... ...and he cares about the rest
- 10. Using Puppet? Idempotency outof the box :-) Try `--help` or the documentation for more information Same for Kickstart!
- 11. Let's try itout!
- 12.
- 13. Icinga Director's targetaudience fully automated environments point & click users at the very same time (!!)
- 14. Show me theclick thingy!
- 15.
- 16.
- 17. Architecture • How andwhere to attach • How does it talk to my Icinga nodes • Masters, Satellites, Agents?
- 18.
- 19. Protocol • Uses theIcinga 2 API (TLS, REST) • Ships whole config, not single objects • This is ways faster with lots of objects • Could still ship partial changes
- 20. Communication Paths • Directortalks to your master node(s) • Deploys always to the very same node • Knows agents / satellites • Controls them via config distribution
- 21.
- 22. Import & Sync •Bomb it with your data • Do not really care about sync details
- 23. Automate all thetasks • Import, Sync and Config Deployment • Granular control. Automatic Deployment only at office hours and not more then one deployment every 10 minutes? Sure, why not.
- 24. Icinga loves automation •Director is a perfect fit for Puppet • Collecting resources with Puppet is slow • Faster: sync from PDB • Exporting resources? • Use Director as your collector!
- 28.
- 29. Impossible, show mea demo
- 30.
- 31. Director offers aREST API • Simple and powerful • Easy and intuitive to use • Assists you with the trickiest part of the job: detect and handle changes
- 40. Monitoring has to„just work“ • No one wants to waste time on it • But not every system is fully automated • e.g. „Add a new MSSQL instance“ • Environmental sensors
- 41. Deploying every fewminutes? • Don't want to wait for next Puppet run? • New hosts or apps need to be actively monitored seconds after being deployed
- 42.
- 43. HOW CAN YOUUSE DIRECTOR?
- 44. Lots of datasources? Directoris your single source of truth CMDB has a lot of infomation... ...but not everything ...and somewhat outdated Use it nonetheless Enrich it with other sources
- 45. Using Satellites? • Usetemplates with defined Zone • Config flows top-bottom • Commands and templates are usually still deployed to the global zone • You can override those decisions on any object at any time
- 46. Running Icinga 2Agent? Do not care about Zones and Endpoints They are autocreated Provided certificate signing tickets Generated customized icinga2.conf
- 47.
- 48. Director is highlymodular Current Hooks: DataType, ImportSource, PropertyModifier, ShipConfigFiles Even Directors own implementations extend and use them to provide you nice real-world examples
- 49.
- 50.
- 51. Code https://www.github.com/Icinga → icingaweb2-module-director https://www.github.com/Thomas-Gelf → icingaweb2-module-aws →icingaweb2-module-puppetdb → icingaweb2-module-fileshipper
- 52.
- 53.