Ok, so to be clear, users will still log on to each printer individually and upload their jobs to OctoPrint? If all it is doing is “monitoring” the printers, then I don’t see any reason for complicating things further with even more (closed source cloud based) software.
OctoPrint already logs every print job and start/finish notifications into Discord. When I finish the SSO system for the portal, we can set it up so members have to login to use OctoPrint so we can track who is using them. What benefits does 3DPrinterOS give us over this?
If you’re wanting to collect detailed usage metrics about each printer then a much better way would be to install this OctoPrint prometheus plugin. I’m happy to setup an instance of InfluxDB or similar on porthack01 which would allow us to collect extremely detailed metrics and make customisable reports and dashboards using something like grafana.
Example grafana dashboard:
That prometheus plugin exports the following data:
python version - as info
octoprint version, hostname, os - as info
actual temperature - as gauge with tool identifier label
target temperature - as gauge with tool identifier label
client number - as gauge; the actually connected clients to the host
printer state - as info
started prints - as counter
failed prints - as counter
done prints - as counter
cancelled prints - as counter
timelaps count - as counter
print progress - as gauge with path label
slice progress - as gauge with path label
print total time - as counter
last print time - as gauge
fan speed - as gauge
extrusion total - as counter
x, y and z travel - as a counter
last print extrusion - as gauge
If we’re still using OctoPrint in the same way as before, I don’t know why you feel this way. If you want to jump in and set everything up before I get a chance then go for it. But I want to get all of the Pis setup ASAP so the printers are more reliable and usable. If you’re still keen on integrating with 3DPrinterOS, then there’s nothing stopping you from installing the plugin after OctoPrint is setup.