I have decided to release my program for viewing node statistics to a wider audience. Around a dozen people have been using it for over 2 years.
The program is written in Delphi Community Edition.
It is open source and the code is available at the following link: https://bitbucket.org/RealSHELS/storjnodeviewer/src/master/Viewer/
It only needs the dashboard port.
The app displays the same data as the dashboard, just in a different view.
The initial idea is to display the nodes data grouped in a tree structure.
Is this only for windows based nodes running locally on the same PC as this software?
Can’t seem to find anywhere to add network addresses for nodes.
Then in Tree Settings window you need create structure with your storjnodes.
Example on screenshot. I’m add Total as main treenode. Then sub treenode PC1, and in PC1 sub treenodes with ip and port to dashboard.
Oh no! This value is harder to support due to the interfaces I had available abstracting the hashstore from the piece store, and I didn’t find any reference to it in the storj/storj repo, so I removed it.
Is the data actually used in the program or does it just fail parsing because the key was removed from the response?
From quick peek at source yes it seems group & node data come from NodeData.DiskSpace.Used while for the leaf satellite nodes it appears to come from Satellite.StorageUsed aka currentStorageUsed – circled red. (Hope that’s right )
Personally I don’t depend on satellite-level detail all that much if the tool was updated to ignore it. Reviewing the other graphana thread might help assess usefulness in the wild. Thanks!
Project i work on , storjdashboard.com that actually shows satellite specific usage along with full node disk usage… I guess that won’t be possible going forward from v1.122.1?
I think so, it’s permanent. We didn’t find relations to that code, so it was removed as redundant.
It could be returned back though, but would take more time, because it’s not so easy to split that data if you would use a hashstore backend. It also influenced the wrong usage and free space reporting.