A simple website where SNO can check the up-to-the-minute information on service availability (satellite offline, etc) is a must in any enterprise solution.
1 Like
A page showing network wide stats would be implemented in due time from what I remember was said in rocketchat
I fully agree.
Any node operator with a signed identity should be able to get detailed information about availability and expected downtime of the satellite nodes. There should also be an Internet based web portal available where SNOs can login and ping their own node for simple live network verification and simple troubleshooting.
A locally generated web page with the words “Online” is not very helpful. Just today, one of the satellites went offline for a while. It happened to be the only satellite that is sending/receiving data to my node. The log file is unclear in trying to figure out “Hey! Is this my problem or their problem?” … So, I checked storjnet.info and noted that the satellite was down… “Whew! Not my problem.”
1 Like
I just want every SNO to know a satellite is not just 1 computer, its a group of servers.
I understand that quite well.
However, there is one satellite ID for each satellite substation. All traffic is tagged with this single ID. And zero traffic occurs if that single ID is not communicating with the SNOs.
So, while it is true that there is quite a bit of complexity sitting behind that single ID, every SNO is waiting for timely, easily identified, and concise information as to the following:
- Is my SN fully operational?
- Is the satellite substation operational?
- If 1 and 2 are true, why has my node traffic dropped suddenly from 288 orders per time frame down to 5 or 6 orders per time frame?
- And various other basic questions that any given server admin might be curious about…
At the end of the day, being an SNO comes down to economics. Is it worth it to run the node?
In my particular case, my node was being vetted. This is fine, and a good practice for any network opening itself up to the general public running pieces of that network. It seemed as if the vetting process was complete when I saw a very large uptick in traffic in the last week.
However, there’s no real clear indication that the node is or is not in a “Being Vetted” category. Sure, I can pull the database (s) and page through the tables to find the column that shows “disqualified” and make the assumption that a NULL in that column means my node is still OK. But this is not clear, concise, nor easy to find.
Perhaps, the internal web based dashboard would give an indication that my node has been disqualified, if such an event happened… But there doesn’t appear to be a indicator showing that the node is actually in good standing order. Is “no news good news” ? … No, not for a system admin. No news is no information. And a system admin is going to be looking for some method of ensuring things are all functioning properly. In this regard, I give the SNO software an “F” …
As a newly minted SNO meeting at least the minimum requirements in all categories, including node uptime of at least 99.3% , I except to be compensated for at least my electricity use once the vetting process has been complete. If my SN is not receiving traffic, for whatever reason, I need to know what that reason is… and I don’t want to be required to discover an Internet forum and post a question about whether or not one of the 4 possible satellite substations is operational. I want that information to be available in a timely manner… clearly presented… and visible on whatever interface is the default interface for an SNO to be looking at.
So…
If the Germany satellite substation composed of K number of computing systems is down for reason FOO, I expect FOO to be displayed somewhere on my node’s interface.
Otherwise I’m going to be looking through the logs, and I’m going to find something like this:
2019-10-05T23:30:07.834Z ERROR orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW failed to settle orders {"error":
2019-10-06T00:30:04.526Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {"count": 288}
2019-10-06T00:30:04.526Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"count": 4}
2019-10-06T00:30:04.526Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S sending {"count": 1}
2019-10-06T00:30:04.761Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW finished
2019-10-06T00:30:04.762Z ERROR orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW failed to settle orders {"error":
2019-10-06T00:30:04.772Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S finished
2019-10-06T00:30:05.061Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2019-10-06T01:30:04.528Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"count": 5}
2019-10-06T01:30:04.528Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {"count": 288}
2019-10-06T01:30:04.754Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW finished
2019-10-06T01:30:04.754Z ERROR orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW failed to settle orders {"error":
2019-10-06T01:30:04.963Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2019-10-06T02:30:04.527Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S sending {"count": 3}
2019-10-06T02:30:04.527Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {"count": 288}
2019-10-06T02:30:04.527Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"count": 4}
2019-10-06T02:30:04.755Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S finished
2019-10-06T02:30:05.058Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2019-10-06T02:30:16.945Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW finished
2019-10-06T03:30:04.520Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {"count": 1}
2019-10-06T03:30:04.520Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"count": 3}
2019-10-06T03:30:05.020Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2019-10-06T03:30:05.090Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW finished
2019-10-06T04:30:04.521Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"count": 1}
2019-10-06T04:30:05.024Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2019-10-06T05:30:04.520Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S sending {"count": 1}
2019-10-06T05:30:04.520Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"count": 5}
2019-10-06T05:30:04.520Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {"count": 3}
And I’m going to Assume that the satellite substation that was having Technical Difficulties is now in a test mode. But perhaps, there’s an algorithm change… and my assumptions are incorrect. Perhaps the algorithm change means my SN, while not disqualified in any way, will not be economical viable to run.
As I wrote in another thread, “I don’t like being in the dark”
1 Like
I responded, but for a reason unknown to me, the forum algorithm marked my post as possible spam.
I think your reply is above your comment
It is now…I guess it was reviewed and accepted as not spam… thanks for the indication.