17 messages in ru.sysoev.nginxRe: Is it possible to monitor the fai...
FromSent OnAttachments
Robbie AllenJun 27, 2008 5:22 pm 
Alexander StauboJun 27, 2008 5:39 pm 
Robbie AllenJun 27, 2008 6:08 pm 
Rt IbmerJun 27, 2008 6:54 pm 
mikeJun 27, 2008 11:02 pm 
Grzegorz NosekJun 28, 2008 4:50 am 
Grzegorz NosekJun 28, 2008 5:31 am 
mikeJun 28, 2008 9:14 am 
Alexander StauboJun 28, 2008 12:28 pm 
Grzegorz NosekJun 28, 2008 12:53 pm 
Almir KaricJun 28, 2008 1:30 pm 
Brice FigureauJun 28, 2008 2:36 pm 
Alexander StauboJun 28, 2008 4:02 pm 
Rt IbmerJun 28, 2008 9:38 pm 
Grzegorz NosekJun 29, 2008 10:57 am.patch, .patch, .patch
Brice FigureauJun 30, 2008 12:23 pm 
Grzegorz NosekJun 30, 2008 12:49 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Is it possible to monitor the fair proxy balancer?Actions...
From:Almir Karic (almi@public.gmane.org)
Date:Jun 28, 2008 1:30:58 pm
List:ru.sysoev.nginx

On Sat, Jun 28, 2008 at 09:54:06PM +0200, Grzegorz Nosek wrote:

The question wasn't really caused by the perceived impossibility of the task :) A status page is certainly simple enough (i.e. fits in the nginx model somewhat), though it has the disadvantage that you have to poll it periodically. I don't think that a dedicated socket for querying backends is a good design for nginx, so I'd like to gather ideas about how to notify the outside world. A log message? Sending a signal somewhere? An SNMP trap? Every way has its advantages and disadvantages, so I'd like to pick the one that sucks the least.

i don't know anything about nginx internals, but i'd imagine the possible way is a control socket through which the controlling program connects to nginx (it can be used as two way communication).