pcca-matrix
commented
6 years ago @DigitalPackrat
Thank you for your support.
1.Graphs per node
Graphs per worker is a good idea, but combined into main graph will be difficult to read if there are many workers.
I will add to the list of workers a small graph of the last 12 hours plotting hourly.
2.Notifications for each node.
added to worklist.
Using smtp for email and growl/prowl for mobile push notification.
trigger when worker is disconnected for more than x minutes and/or when 24h average hashrates drop for more than X percents.
This looks like a great enhancement to proxy monitoring. Sent you a small token of my appreciation via xmr.
A great feature for the future would be individual node monitoring. That would come in two entities.
1) Graphs per node or perhaps the main graph showing all nodes stacked where you could see the entirety of the hash but individual lines for each connected node.
2) Notifications for each node. This would be something selectable for anyone running a mining node just when idle. The general idea is sending an alert probably via email when hash rate suddenly drops for a node. So miner1 nominal hashrate over 24hrs is 400 average and suddenly drops to 300 or 0 an email is sent and the recipient knows to check out that node for issues. Expanding on that, some ISP's block sending email directly over port 25 so specifying a SMTP server with a login and password would be necessary.