Hi Spencer, Have you looked at the XMLRPC API for Supervisord? http://supervisord.org/api.html
With this it's quite easy to remotely query status and stop|start processes. You can do this for multiple instances of supervisord quite easily. Cheers, Phil On Tue, Oct 2, 2012 at 3:08 PM, Spencer Liechty < spencer.liec...@adbucket.com> wrote: > Hey all, > > I've been using supervisord to run persistent scripts on my web > application servers, and am wondering what best practices exist for a > couple of challenges I'm facing. > > 1. Process Logging: I'm currently logging all process logs locally to > /var/log/supervisor/ on my app servers. Does supervisor > suggest/provide a standard way to retrieve those logs from my various > servers? I suppose I could scp that directory daily/weekly/etc, but am > wondering if there exists a canonical supervisor-approved way of > aggregating those logs. > > 2. Process Monitoring/Management: I know I can set up > inet_http_servers on every web server I'm running and manage processes > by simply navigating to each server's supervisorctl web interface, but > I was wondering if there was a way to manage all my different > supervisord servers from a central location. For example, I have 10 > app servers running supervisord on each one, and would like to restart > all processes on all servers. Any ideas on an easy/scriptable way to > do this? Would y'all suggest thinking of dev op tools for activities > such as this? > > Thanks for the help! > Spencer > _______________________________________________ > Supervisor-users mailing list > Supervisor-users@lists.supervisord.org > http://lists.supervisord.org/mailman/listinfo/supervisor-users >
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org http://lists.supervisord.org/mailman/listinfo/supervisor-users
