I use the director to automatically create new hosts imported from the Active Directory or vCenter.
But mostly the systems are not 100% ready to be monitored at that moment. So, messages from Icinga will be send to your mailbox and assigned to a colleague of mine. In many cases that colleague is not the one that is installing the system and so he is wasting time to figure out what’s the problem.
I already found the following topic…
…but I don’t see a real solution in it. Setting an infinitive downtime is probably the worst solution I can imaging, because we all humans who tend to forget things (removing the downtime in this case).
My idea was to create a database trigger (mariadb in my case) on recently added hosts in order to set a downtime. Is it enough to create the downtime it the database and trigger a redeploy afterwards?
Another idea is to configure the director database as an import source for the director. Assessing the table for logging the activities, will show me the recently created hosts. The director can then be used to add the downtime. But looping the whole process might lead to more problems.
Does anyone already have a solution for that or can help me to create the SQL trigger?