Hello staff,
I come with a recurrent topic but I rarely saw go forward here in
list and the zabbix forums .... maybe someone has a better idea or test the
scenario that I describe and tell me it may be a bug.
Okay, I need to measure two types of SLA of the server (physical) and
service.
So far great.
What was I decided to make the following, to measure whether the service is "on air", connected
or at least working I use the trigger that makes a ping on the server,
standard templates for linux and windws (X server is unreachable), and services use
the triggers that measure the service.
Nice, but look what happens if I disconnect the server (physical) to trigger "x server
is unreachable "will become active and start the SLA, therefore the
services also have to start counting, however, when the trigger is active, the zabbix can not obtain the information of the agent and does not monitor the
services, ie zabbix to monitor, not to the SLA and the service only to the SLA server (physical).
The scenario is this, if someone can do a little test would be very grateful.
Set up two triggers only, the default templates, create a tree of sla
for servers and services, place the trigger associated with the server as "server
x unreachable "and the trigger for the service related to it, turn off the server and I confirm that the two SLA's are being calculated, and the SLA of the server service. If they are being monitored can be a problem here with my zabbix, if not, may actually be a bug.
Moreover, I would like suggestions for monitoring the server physically or
is, if it is connected or not, not by the trigger "x server is unreachable."
Thank contributions ...
Regards
Flamarion Jorge
I come with a recurrent topic but I rarely saw go forward here in
list and the zabbix forums .... maybe someone has a better idea or test the
scenario that I describe and tell me it may be a bug.
Okay, I need to measure two types of SLA of the server (physical) and
service.
So far great.
What was I decided to make the following, to measure whether the service is "on air", connected
or at least working I use the trigger that makes a ping on the server,
standard templates for linux and windws (X server is unreachable), and services use
the triggers that measure the service.
Nice, but look what happens if I disconnect the server (physical) to trigger "x server
is unreachable "will become active and start the SLA, therefore the
services also have to start counting, however, when the trigger is active, the zabbix can not obtain the information of the agent and does not monitor the
services, ie zabbix to monitor, not to the SLA and the service only to the SLA server (physical).
The scenario is this, if someone can do a little test would be very grateful.
Set up two triggers only, the default templates, create a tree of sla
for servers and services, place the trigger associated with the server as "server
x unreachable "and the trigger for the service related to it, turn off the server and I confirm that the two SLA's are being calculated, and the SLA of the server service. If they are being monitored can be a problem here with my zabbix, if not, may actually be a bug.
Moreover, I would like suggestions for monitoring the server physically or
is, if it is connected or not, not by the trigger "x server is unreachable."
Thank contributions ...
Regards
Flamarion Jorge
Comment