Systems and methods for GSLB remote service monitoring
The present invention provides improvements to the integration between a metric exchange protocol and a monitoring mechanism supporting load balancing by a Global Server Load Balancing (GSLB) appliance in a GSLB hierarchy of appliances, using a method for triggering a monitor on a remote service. The method includes receiving, by a first appliance, metrics of a second appliance via a metric exchange connection between the first and second appliances. The first appliance includes a GSLB service and identifies a service provided via the second appliance as a remote service for GSLB. The first appliance may identify via the metrics that a state of the service is up, and determine that the metric exchange connection is down. Responsive to the determination, the first appliance may trigger a monitor to monitor the status of the service. Further, the first appliance may obtain via the monitor a second status of the service.
1. A method for triggering a monitor on a remote service of a Global Server Load Balancing (GSLB) appliance in a GSLB hierarchy of appliances, the method comprising:
a) receiving, by a first appliance, metrics of a second appliance via a metric exchange connection between the first appliance and the second appliance, the first appliance comprising a GSLB service and identifying a service provided via the second appliance as a remote service for GSLB;
b) identifying, by the first appliance, via the metrics that a state of the service provided via the second appliance is up;
c) determining, by the first appliance, that the metric exchange connection is down;
d) triggering, by the first appliance responsive to the determination, a monitor to monitor the status of the service provided via the second appliance; and
e) obtaining, by the first appliance, via the monitor a second status of the service.
2. The method of claim 1 , wherein step (d) further comprises enabling, by the first appliance responsive to the determination, the monitor bound to the service.
3. The method of claim 1 , wherein step (e) further comprises determining, by the first appliance, via the monitor that the second state of the service is up.
4. The method of claim 1 , wherein step (e) further comprises determining, by the first appliance, via the monitor that the second state of the service is down.
5. The method of claim 1 , wherein step (c) comprises determining that the metric exchange connection is up and that the second appliance identifies a state of the service provided via the second appliance as down.
6. The method of claim 5 , wherein step (c) further comprises identifying that an effective state of the service provided via the second appliance is down.
7. The method of claim 5 , wherein step (c) further comprises identifying that an effective state of the service provided via the second appliance is up.
8. The method of claim 1 , wherein step (d) comprises identifying, by the first appliance, a monitor bound to the service provided via the second appliance.
9. The method of claim 1 , wherein step (b) further comprises identifying via metrics of the second appliance that a state of the service is up if one or more servers associated with the service is running.
10. The method of claim 1 , wherein step (b) further comprises identifying via metrics of the second appliance that an effective state of the service is down if a threshold of the service has been exceeded.
11. A method for triggering a monitor on a remote service of a Global Server Load Balancing (GSLB) appliance in a GSLB hierarchy of appliances, the method comprising:
a) receiving, by a first appliance, metrics of a second appliance via a metric exchange connection between the first appliance and the second appliance, the first appliance comprising a GSLB service and identifying a service provided via the second appliance as a remote service for GSLB;
b) identifying, by the first appliance, that the metric exchange connection is up;
c) determining, by the first appliance, that a state of the service of the second appliance is down and that the effective state of the service is down, the state indicating whether at least one server of the service is up, the effective state indicating whether the service has exceeded a threshold;
d) triggering, by the first appliance responsive to the determination, a monitor to monitor the status of the service provided via the second appliance; and
e) obtaining, by the first appliance, via the monitor a second status of the service.
12. The method of claim 11 , wherein step (d) further comprises enabling, by the first appliance responsive to the determination, the monitor bound to the service.
13. The method of claim 11 , wherein step (e) further comprises determining, by the first appliance, via the monitor that the second state of the service is up.
14. The method of claim 11 , wherein step (e) further comprises determining, by the first appliance, via the monitor that the second state of the service is down.
15. The method of claim 11 , wherein step (c) comprises determining that the metric exchange connection is down.
16. The method of claim 15 , wherein step (d) further comprises triggering the monitor responsive to the metric exchange connection being down.
17. The method of claim 11 , wherein step (c) comprises determining that the metric exchange connection is up and that the second appliance identifies a state as down and an effective state as up.
18. The method of claim 11 , wherein step (d) comprises identifying, by the first appliance, a monitor bound to the service provided via the second appliance.
19. The method of claim 11 , wherein step (c) further comprises determining via metrics of the second appliance that the state of the service is up if one or more servers associated with the service is running.
20. The method of claim 11 , wherein step (c) further comprises determining via metrics of the second appliance that an effective state of the service is up if a threshold of the service has not been exceeded.