I like to keep things public why not post it so anyone cant take a look and test it? I think everyone is looking at better and easier ways to monitor there nodes.
We’re currently still in development/testing stages but we’re keen to get some SNOs onboard and tell us what things they’d like to be able to see at a glance/easily accessible…
It would be a lot easier to have this as a docker image. I’m not really happy with installing it in root and having to also install nginx and PHP. This would also make it easier to install on windows.
To be honest, I’m also not really thrilled about having to expose any stats publicly on an open port, without authentication.
One of the things we are looking to create is a HTTP Authentication between the checking servers and your NGINX so that a specific header with a key/hash is required to be able to see the json data.
Currently looking into the Windows install for NGINX/PHP and creating some automated batch for people to easily use for install/setup
Installing in the / (root) location is simply just for logging and to make it easy to find however in future setup may look to place them into /var/log/
I agree with this. It’s open source, so anyone could contribute to it instead of making their own dashboard. And multinode uses the storage nodes native authentication as well, keeping it all in the hands of the SNO.
Hii @Pac@jammerdan@BrightSilence
Appreciate your feedback on this so far, however this dashboard is quite abit different - I don’t have any screenshots to hand… but when I have chance I will post here for yourselves and others to make decisions…
I dont agree I do not use the multidashboard because its trash. It doesnt even compete with my loki dashboard… I want more information about my node aka audits errors logs etc, the amount of money difference I make per day. So more people who wanna improve on there own dashboard the better it will be because people like to work on there own projects vs improving someone else… Plus storj tracks the multidash and I do not like any type of tracking.
I’ve got my own dashboard as well. It’s console-based, not web-based, and it also integrates OS statistics like bandwidth used as measured by the kernel, system logs, some kernel-level I/O stats, data from temperature sensors… Integrating all that data into the multinode dashboard would be a huge task, and I wouldn’t even be able to test it on platforms other than Debian. Nothing wrong with making one’s own.
There is of course room for other solutions. My objection isn’t that someone built their own dashboard. I mean, I created an earnings calculator to display data not easily available on the regular dashboard myself. My objection is that this is externally third party hosted and I’m sending data to a closed source server. In my opinion this is going about it the wrong way and I would be handing over my data without knowing what happens to it. And for now it even exposes that data publicly on my IP. (Though it’s good to hear that is being worked on to resolve it)
Edit: In fairness to @ItsHass, it’s clear from the github that the script does strip out node ID and wallet ID locally. But is that enough?