You could use the conky-cli build (without the X dependency). You could then run it and pipe the output into some file that you serve statically. Hmmm may spend some time investigating.
To follow up with this. You could add `conky -c json.conky | while read json; do echo $json > /opt/http/monitor/info.json; done` to your start. Then just static serve the `info.json` file and it should update at whatever interval you set for conky. No dynamic execution though (hard part is that lack of interaction).
Comments
Not much different than conky...except the web service part.
http://conky.sourceforge.net/
You could use the conky-cli build (without the X dependency). You could then run it and pipe the output into some file that you serve statically. Hmmm may spend some time investigating.
To follow up with this. You could add `conky -c json.conky | while read json; do echo $json > /opt/http/monitor/info.json; done` to your start. Then just static serve the `info.json` file and it should update at whatever interval you set for conky. No dynamic execution though (hard part is that lack of interaction).
Can I use conky to monitor a remote server? I'd like that.
Of course! ssh -X. Obviously requires conky (and a minimal X server) on the server.
no offense, I think that's effectively 'no'. :)
no one is running an X server on their production servers, perhaps unless somehow related to their actual purpose (screenshots, ui testing, etc.)
P.S. I agree this is pointless. The best solution in my opinion is simply ssh and [h]top or glances.
Eh, I was hoping to do it without running x on the remote server.