Peter Eckel <[email protected]> writes: > Would it be an option to use the API to disable monitoring when a Test/Dev > host is taken down (e.g. using a shutdown script) and re-enable it when it is > brought up again?
We were in a similar situation and have implemented this via the send_ncsa command. Works reliable. Rgeards, Wolfagng > This would still provide full monitoring and alerting as long as the host is > running, and if a machine crashes or otherwise becomes unavailable, but not > during planned downtime indicated by server shutdown. > >> On 16 Jun 2016, at 01:11, Felix Cruz <[email protected]> wrote: >> >> No expert here, but if they can power off at anytime, then how would >> Icinga distinguish a power off from a host down? You'd have to be >> able to monitor for power status directly at the power socket. Even >> then, how would you know if the power off status was intentional or >> not? >> >> Tel them if they want monitoring it stays on, or as the previous person >> said, why bother monitoring? >> >> Sent from my iPhone >> >> On Jun 15, 2016, at 7:34 AM, Pascal Larivee <[email protected]> wrote: >> >>> My question would be then, why monitor them at all? Or you could set then >>> in a "qa" group that sends no alert at all, only viewable on the web >>> interface >>> -- >>> Pascal Larivée >>> Senior IT Architecture & Cloud Ops Engineer >>> Internap >>> >>> Unfortunately interval time may not be the best method since dev/qa >>> people can power their servers on and off when they want. So they >>> could power them on for the weekend if they're working, or they may >>> power them off during a workday if they have the day off. >>> >>> On Wed, Jun 15, 2016 at 7:21 AM, Gunnar Beutner <[email protected]> >>> wrote: >>> Hello, >>> >>> There are two things you could do about that: >>> >>> 1. Set the check_period attribute for those Host and Service objects – this >>> way Icinga will only run checks during whatever interval you specify in >>> that TimePeriod object. >>> 2. Set the period attribute for whatever Notification objects you >>> have for those hosts and services – that way Icinga will still >>> check those hosts and services, however it will only send >>> notifications according to the intervals in the TimePeriod object. >>> >>> Kind regards, >>> Gunnar >>> >>> On 15/06/16 13:16, "icinga-users on behalf of Matt Shields" >>> <[email protected] on behalf of [email protected]> wrote: >>> >>> I have Icinga setup to monitor our production instances in AWS, but >>> we also have dev/qa resources that get shut off every night. I >>> haven't been monitoring them because as soon as they power off I >>> get flooded with alerts. >>> >>> >>> Is there a way to monitor servers only when they are powered on? >>> >>> >>> Thanks >>> Matt > > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
