server / service down notification?
-
Most of the open source solutions will do this. But if you need it quick you can do this with Powershell or Bash.
-
This is for servers inside a firewall. On some of them we just need to know if they have been down for more than a reboot. On others we need to get a notification if a certain service goes down.
-
I'd rather not do some kind of powershell thing because if the server or ISP goes down, I won't get an alert.
-
Zabbix or Nagios seem a bit heavy for this, but maybe either of those are worth a look?
-
@Mike-Davis said in server / service down notification?:
I'd rather not do some kind of powershell thing because if the server or ISP goes down, I won't get an alert.
So you'll want to do something off the network? Centreon, Nagios, or Zabbix, are all pretty capable of doing this. You'll just need to open the monitoring port on the firewall to the monitoring server.
-
It pretty much has to be off network. We have a number of clients with 20+ servers. Some of them have redundant ISP connections, some don't. We don't want something that is going to send us 20 alerts telling us that 20 servers are down if the internet connection is down. On the other hand, we would like an email telling us that the entire site is down. The simple ping tests that are used for web servers won't work because most of the servers are not internet facing.
-
@Mike-Davis said in server / service down notification?:
It pretty much has to be off network. We have a number of clients with 20+ servers. Some of them have redundant ISP connections, some don't. We don't want something that is going to send us 20 alerts telling us that 20 servers are down if the internet connection is down. On the other hand, we would like an email telling us that the entire site is down. The simple ping tests that are used for web servers won't work because most of the servers are not internet facing.
Not sure about this then, you'd probably still get the server errors in addition to the entire site being down. If you allow the port (Zabbix uses 10050 and 10051 for instance) you can make your monitoring available from offsite.
-
@coliver said in server / service down notification?:
@Mike-Davis said in server / service down notification?:
It pretty much has to be off network. We have a number of clients with 20+ servers. Some of them have redundant ISP connections, some don't. We don't want something that is going to send us 20 alerts telling us that 20 servers are down if the internet connection is down. On the other hand, we would like an email telling us that the entire site is down. The simple ping tests that are used for web servers won't work because most of the servers are not internet facing.
Not sure about this then, you'd probably still get the server errors in addition to the entire site being down. If you allow the port (Zabbix uses 10050 and 10051 for instance) you can make your monitoring available from offsite.
You can also set up a small Zabbix Proxy for this too. That way firewall ports only go to one machine, and IIRC, the Proxy can encrypt the traffic.
@Mike-Davis said in server / service down notification?:
We don't want something that is going to send us 20 alerts telling us that 20 servers are down if the internet connection is down. On the other hand, we would like an email telling us that the entire site is down. The simple ping tests that are used for web servers won't work because most of the servers are not internet facing.
In Zabbix, you can set up trigger (alert) dependencies... so that if >15 servers at the site are up, then it's not a site wide problem, so only alert for the 5 servers that are down.
If there are > 15 servers DOWN, then it probably is a site wide problem, send the site-wide alert...
Plus, with Zabbix, you can check for any service to be started / stopped, etc.
-
@dafyre said in server / service down notification?:
@coliver said in server / service down notification?:
@Mike-Davis said in server / service down notification?:
It pretty much has to be off network. We have a number of clients with 20+ servers. Some of them have redundant ISP connections, some don't. We don't want something that is going to send us 20 alerts telling us that 20 servers are down if the internet connection is down. On the other hand, we would like an email telling us that the entire site is down. The simple ping tests that are used for web servers won't work because most of the servers are not internet facing.
Not sure about this then, you'd probably still get the server errors in addition to the entire site being down. If you allow the port (Zabbix uses 10050 and 10051 for instance) you can make your monitoring available from offsite.
You can also set up a small Zabbix Proxy for this too. That way firewall ports only go to one machine, and IIRC, the Proxy can encrypt the traffic.
@Mike-Davis said in server / service down notification?:
We don't want something that is going to send us 20 alerts telling us that 20 servers are down if the internet connection is down. On the other hand, we would like an email telling us that the entire site is down. The simple ping tests that are used for web servers won't work because most of the servers are not internet facing.
In Zabbix, you can set up trigger (alert) dependencies... so that if >15 servers at the site are up, then it's not a site wide problem, so only alert for the 5 servers that are down.
If there are > 15 servers DOWN, then it probably is a site wide problem, send the site-wide alert...
Plus, with Zabbix, you can check for any service to be started / stopped, etc.
I had Nagios setup in the past but Zabbix looks to be a bit more powerful.
-
OpenNMS, Spiceworks Network Monitor, Nagios
