14 messages in ru.sysoev.nginxRe: Feature requestED: monitoring Ngi...
FromSent OnAttachments
François BattailApr 30, 2008 12:29 pm 
Manlio PerilloApr 30, 2008 1:16 pm 
François BattailApr 30, 2008 1:39 pm 
Manlio PerilloMay 1, 2008 1:30 am 
François BattailMay 1, 2008 1:58 am 
Manlio PerilloMay 1, 2008 2:39 am 
François BattailMay 1, 2008 5:42 am 
Rt IbmerMay 1, 2008 9:59 am 
Grzegorz NosekMay 1, 2008 11:35 am 
Manlio PerilloMay 1, 2008 11:57 am 
François BattailMay 1, 2008 1:25 pm 
Manlio PerilloMay 2, 2008 1:52 am 
François BattailMay 2, 2008 6:50 am 
Rt IbmerMay 2, 2008 10:31 am 
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: Feature requestED: monitoring Nginx from the outsideActions...
From:François Battail (fb-f@public.gmane.org)
Date:Apr 30, 2008 1:39:03 pm
List:ru.sysoev.nginx

Manlio Perillo <manlio_perillo@...> writes:

Good.

Thanks.

When actually happens the running phase? At the end of the HTTP request? At regular intervals?

I've set a hook in logging phase.

Note that since you don't know when a variable will be updated, you may miss important changes in the variable.

Yes, but it's monitoring, not real time.

As an example, in the upstream module if a peer is down, the variable peer.down will be set to 1, but if *all* the peers are down, then all the variables are set to 0, for a fast restart in the successive request.

It's a side effect, sorry I'm in the logic on monitoring.

4) Scripts

I can't see any form of synchronization here.

Correct, but it's monitoring not real time, value fetch is atomic and so it's coherent at a given moment. Nginx is write only and use ngx_atomic_t variables; it's a snapshot at a given moment. Well can I said it's just monitoring ;-)

Thank you for your input,

Best regards.