This application is a backend/frontend system to remotely control multiple Zabbix servers (http://www.zabbix.com/).
- Issues list sorted by Severity -> Last Change
- Issues treemap overview, with drilldown per server
- Dynamic filtering on issues list through interaction with treemap objects
- Redirect to issue details from issues list
- NEW! Zabbix servers configuration management, ability to add, remove and choose credentials!
- NEW! Notification to all connected users on configuration changes (like the servers one)
Pull the image and run it:
docker pull quadrata/octozab docker run -it -d -p $frontendHostPort:80 -p $backendHostPort:8080 --name="octoZab" skundef/octozab
where $frontendHostPort and $backendHostPort are ports on your host where you desire that frontend and backend respectively should run.
Now you have to configure a bit the container. Attach to it and start necessary services:
docker attach octoZab
service httpd start service octozab-redis start service octozab-node start
"/var/www/html/octozab/config.js" with your host url and host backend port you defined above at container run.
IMPORTANT! When we speak about host, it is meant host, not the container. So above with $frontendHostPort and $backendHostPort we were referring to host ports on which are mapped container ports. And with host url in "config.js" we mean the url on which you access your host, not the container.
Then detach from container with Ctrl+P-Ctrl+Q.
That's it! Now you should be able to connect to application browsing at
http://yourHostUrl:yourHostFrontendPort/octozab (if you mapped container port 80, frontend one, with port 80 on your host, you can omit the
:yourHostFrontendPort url part).