I Would like the resources to become DOWN/UP on a single monitoring failure/success.
Historically gdnsd decides resource status monitoring a single route, what is fine for LAN but not that great for WAN -- it is common a resource that seems perfect from local monitoring POV but actually it is not available from some locations.
Using EXTMON you are empowered to build an application that uses heuristics / several rules to decide if a resource should be UP or DOWN.
1. Using multiple external monitoring stations. Checking the resource availability from several routes may give a level of confidence that a resource must be turned active or inactive immediately.
2. Resource usage monitoring or server management may decide that new requests must be processed by another server (e.g. DoS, high load, high latency, packet loss, emergency maintenance, etc). It already may be done with elegance using "http_status" and returning "ok_codes" meaning UP or DOWN but DANGER precludes immediate action.
3. LAN. Failover of master->slave database servers and controlled failback slave->master.
4. CDNS. Static objects. If you have redundancy, capacity, network proximity, etc, resolving to healthy resources instead to the "dangerous" ones.
Thank you for your attention and time. You developed a great software!
On Friday, August 29, 2014 3:59:26 PM UTC-3, blblack wrote: