On Thu, Jan 20, 2011 at 7:34 AM, Graham Dumpleton <[email protected]> wrote: > If you look, I'd suggest that system monitoring tools which can > capture that information are already available. I don't see a need for > this to specifically be embedded within mod_wsgi. > [ ... ]
i've used or still use nagios, zenoss, munin (and a bunch of other similar tools) that can monitor apache logs and get some decent data but most that i usually get out is just enough to figure out where the problem is, usually domain or process id(s). i also have logs on wsgi application side but it always feels like there is more data between apache monitoring tools and wsgi app logs that could be useful. i was hoping that some mod_wsgi specific data could be extracted, although i'm not sure if it can be useful. > What is your justification for wanting to do this? All I can see is > that you are trying to fit more distinct WSGI applications on a system > than the hardware can perhaps accommodate. :-) let's say i have several machines and i want to move, shutdown and start new wsgi applications between machines. instead of shutting down wsgi application i would like to be able to push application to swap/disk but i'm not talking about OS doing that when wsgi app is not used. if i host a large number of wsgi apps i would like to preload all and freeze on disk to be able to restore them in a fast way. just to mention, i been using apache/mod_wsgi setup that enables me to have wsgi app releases and other stuff i was talking about. other ideas are just some stuff i've been thinking about and are obviously very unclear 8-) Aljosa -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
