On Thursday 16 June 2016 at 14:20:00, Felix Cruz wrote:
> Hi
>
> Process wise it makes no sense to power off machines especially if they
> require monitoring.
Of course it makes sense to power off development machines, when they're not
being used for development. They might need more frequent hardware changes
than production machines, too, which also means more frequent "host down"
situations.
> How would you automate the handling of a random power off event with unknown
> time interval, or distinguish it from a genuine unhandled event that
> requires an action?
I think what the original poster is getting at is that there is a requirement
to monitor *services* such as disk capacity, perhaps network traffic, etc, but
there is no requirement to perform *host* monitoring - if the machine goes off,
no alert is needed, however if the disk gets close to being full, an alert is
required.
As the original email in this thread asked: "Is there a way to monitor servers
only when they are powered on?"
Therefore a power down event is not considered of interest, but no other
alerts are required when the machine is powered down either.
Regards,
Antony.
--
"If I've told you once, I've told you a million times - stop exaggerating!"
Please reply to the list;
please *don't* CC me.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
