Also there's the whole "killing a mosquito with a bazooka" point there. If you are making this for your research-group then all the more reason to not depend on

Also there's the whole "killing a mosquito with a bazooka" point there. If you are making this for your research-group then all the more reason to not depend on a big thing like Zabbix that'd require a fatter server and someone to set up/maintain. For your purposes this looks like more than enough but if you wanted to hone your Pythonic/Flask/webapp skills a little more I'd suggest you expose the rest of the info exposed by the CLI and also expose the backend API for people that may wanna use your underlying code and integrate into their own stuff (eg something that chooses an available GPU before starting a job).