Portal Client: Improve node status log #3327
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that in the Nimbus Portal fleet logs the Portal node status looks like this for the 2GB nodes:
And like this for the 35G nodes:
Using the default storage size of 2G the
radiusPercentage
shows as 0%. This isn't very useful information for the user and the radius is actually likely to get smaller as the amount of data in the network grows.To improve the logs I suggest we use log radius and log radius percent which will be a better way to represent the information. We could either show both the
radiusPercentage
andlogRadiusPercentage
or just show the log radius named as radiusPercentage (log base 2).Also now showing the storage in MB instead of KB.
The updated log looks like this:
Alternatively we could show something like: