Posts in this category
- The Fun of Running a Public Web Service, and Session Storage
- CPAN Pull Request Challenge: A call to the CPAN authors
- You Write Your Own Bio
- Icinga2, the Monitoring System with the API from Hell
- Progress in Icinga2 Land
- Iron Man Challenge - Am I a Stone Man?
- Correctness in Computer Programs and Mathematical Proofs
- Why Design By Contract Does Not Replace a Test Suite
- Doubt and Confidence
- Fun and No-Fun with SVG
- Goodby Iron Man
- Harry Potter and the Methods of Rationality
- Introducing my new project: Quelology organizes books
- iPod nano 5g on linux -- works!
- Keep it stupid, stupid!
- My Diploma Thesis: Spin Transport in Mesoscopic Systems
- Why is my /tmp/ directory suddenly only 1MB big?
Wed, 21 Dec 2016
Progress in Icinga2 Land
Last month I blogged about my negative experiences with the Icinga2 API. Since then, stuff has happened in Icinga2 land, including a very productive and friendly meeting with the Icinga2 product manager and two of the core developers.
My first issue was that objects created through the API sometimes don't show up
in the web interface. We learned that this can be avoided by explicitly specifying the
zone attribute, and that Icinga 2.6 doesn't require this anymore.
The second issue,
CREATE + UPDATE != CREATE isn't easy to fix in Icinga2.
Apply rules can contain basically arbitrary code, and tracking which ones to run,
possibly run in reverse etc. for an update is not easy, and while the Icinga2 developers
want to fix this eventually, the fix isn't yet in sight. The Icinga
Director has a
workaround, but it involves restarting the Icinga daemon for each change or
batch of changes, an operational characteristic we'd like to avoid.
The inability to write templates through the API stems from the same
underlying problem, so we won't see write support for templates soon.
The API quirks will likely remain. With support from the Icinga2 developers, I was able to get selection by element of an array variable working, though the process did involve finding at least one more bug in Icinga. The developers are working on that one, though :-).
Even though my bug report requesting more documentation has been closed, the Netways folks have improved the documentation thoroughly, and there are plans for even more improvements, for example making it easier to find the relevant docs by more cross-linking.
All in all, there is a definitive upwards trend in Icinga2's quality, and in my perception of it. I'd like to thank the Icinga2 folks at Netways for their work, and for taking the time to talk to a very vocal critic.