Hi Mike,
We could REALLY use a way to get the status of upstream servers - in
particular a notification that nginx has declared an upstream server (as
used in load balancing) offline, and a notification that nginx has
detected that a previously unavailable upstream server it took offline
is now back on line.
Thanks!
----- Original Message ----
From: Michał Jaszczyk [email protected]
To: [email protected]
Sent: Thursday, June 12, 2008 6:49:49 PM
Subject: tell me your feature request about nginx
Hi,
It’s me again, the mod_rails/mod_ruby/mod_rack guy :).
As you may remember, I’m a CS student looking for a subject for my
masters thesis :). I had this great idea about making mod_r* for
Nginx, but it turned out to be a bad one…
So… Maybe you have
some ideas about what cool feature could Nginx have? I could implement
it then :).
Regards,
Mike
Hi Mike,
We could REALLY use a way to get the status of upstream servers - in particular a notification that nginx has declared an upstream server (as used in load balancing) offline, and a notification that nginx has detected that a previously unavailable upstream server it took offline is now back on line.
A monitoring tool like Monit already does that isn’t it?
On Fri, Jun 13, 2008 at 1:11 AM, Rt Ibmer [email protected] wrote:
We could REALLY use a way to get the status of upstream servers - in particular a notification that nginx has declared an upstream server (as used in load balancing) offline, and a notification that nginx has detected that a previously unavailable upstream server it took offline is now back on line.
Seconded. A status page such as HAProxy’s (see
http://www.igvita.com/posts/05-08/haproxy-large.png) would be awesome.
More real-time metrics would be extremely handy. These could be used
to plug into tools like Munin.
You could look to Varnish (http://varnish.projects.linpro.no/) for
inspiration here. Instead of logging to files, Varnish uses
low-overhead circular buffers in shared memory to log and output
entries and metrics; this way you can catch the output any way you
like – syslog, files, over the net. (I’m also pretty sure that
Varnish does not output any information unless someone is listening.)
Varnish comes with a few tools that let you track this output on the
terminal. For example, this is the output of “varnishstat”, which is a
top-like tool that updates in real time. Suffice to say, it gives you
tons of useful data:
Another tool is varnishhist, which draws an ASCII diagram of the
response times:
Other tools are varnishlog (gives you a real-time dump of the log) and
varnishtop (a top for log lines – each unique log line is counted and
printed in order of frequency).
Alexander.