Hi,
I don't know if I'm missing something, or it's a real problem.
We had a nobreak problem, and due to it, the server went down, but we didn't received any alerts from zabbix.
I was reviewing host's latest data, and I can see that host status is unreachable, but the others are "normal" (ping is showing up, services are running) but the latest data is from when the server went down.
The normal behavior was to receive an alert from zabbix when the host became unreachable, isn't?
The trigger is properly defined ({xpto:status.avg(#3)}=2) and always worked, before.
Does it have an explanation? Is it possible to avoid this situation?
TIA,
Bob
I don't know if I'm missing something, or it's a real problem.
We had a nobreak problem, and due to it, the server went down, but we didn't received any alerts from zabbix.
I was reviewing host's latest data, and I can see that host status is unreachable, but the others are "normal" (ping is showing up, services are running) but the latest data is from when the server went down.
The normal behavior was to receive an alert from zabbix when the host became unreachable, isn't?
The trigger is properly defined ({xpto:status.avg(#3)}=2) and always worked, before.
Does it have an explanation? Is it possible to avoid this situation?
TIA,
Bob