Supervisord Multi Server Monitoring Tool
- Monitor unlimited supervisord servers and processes
- Start/Stop/Restart process
- Read stderr log
- Start new Redmine ticket when stderr occurs
- Sound alert when stderr occurs
- Mute sound alerts (after some time auto resume)
- Monitor process uptime status
1.Clone supervisord-monitor to your vhost/webroot:
git clone https://github.com/mlazarov/supervisord-monitor.git
2.Copy application/config/supervisor.php.example to application/config/supervisor.php
cp supervisord-monitor/application/config/supervisor.php.example supervisord-monitor/application/config/supervisor.php
3.Enable/Uncomment inet_http_server (found in supervisord.conf) for all your supervisord servers.
[inet_http_server] port=*:9001 username="yourusername" password="yourpass"
Do not forget to restart supervisord service after changing supervisord.conf
4.Edit supervisord-monitor configuration file and add all your supervisord servers
5.Configure your web server to point one of your vhosts to 'public_html' directory. 6.Open web browser and enter your vhost url.
1.Open configuration file:
2.Change this lines with your redmine url and auto assigne id:
// Path to Redmine new issue url $config['redmine_url'] = 'http://redmine.url/path_to_new_issue_url'; // Default Redmine assigne ID $config['redmine_assigne_id'] = '69';
Did not receive a '200 OK' response from remote server.
Having this messages in most cases means that Supervisord Monitoring tools does not have direct network access to the Supervisord RPC2 http interface. Check your firewall and network conectivity.
Did not receive a '200 OK' response from remote server. (HTTP/1.0 401 Unauthorized)
401 Unauthorized means that you have connection between Supervisord Monitoring tool and Supervisord but the username or password are wrong.
Having this message means that your supervisord service doesn't have rpc interface enabled (only for v3+ of Supervisord). To enable the rpc interface add this lines to the configuration file:
From the Supervisord Docs
In the sample config file, there is a section which is named [rpcinterface:supervisor]. By default it looks like the following:
[rpcinterface:supervisor] supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
The [rpcinterface:supervisor] section must remain in the configuration for the standard setup of supervisor to work properly. If you don’t want supervisor to do anything it doesn’t already do out of the box, this is all you need to know about this type of section.
For more information go to the offitial Supervisord Configuration Docs: http://supervisord.org/configuration.html#rpcinterface-x-section-settings
The requested URL /control/ ... was not found on this server.
If you are getting this error on every action (stop, start, restart etc) most probably your web server isn't respecting the .htaccess file found in
To test this you can add
AllowOverride All config to the httpd.conf (if you are using Apache) or to add the rules from the .htaccess file to the httpd.conf file.
- stvnwrgs - added authentication functionality to supervisord monitor
- rk295 - added handling of non authenticated servers
- All Contributors
Who uses Supervisord Monitor?
If you've used Supervisord Monitor Tool send me email to firstname.lastname@example.org to add your project/company to this list.
Copyright (C) 2013 Martin Lazarov
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.