You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The etcd linearization visualization or report json file data is pretty hard to read due to not very readable JSON.
There is a lot of empty fields like "Value": {Value:"123", "Hash": 0}. The reason for that is that we are using dumping data to JSON which is not very human readable. Also JSON in golang by default will serialize all the fields even if they are empty (See Hash field in the example).
As described in #19933 (comment) we might want to also introduce a shorter description of the model. Formatted JSON is very vertical making it not very useful for large state.
What would you like to be added?
The etcd linearization visualization or report json file data is pretty hard to read due to not very readable JSON.
There is a lot of empty fields like
"Value": {Value:"123", "Hash": 0}
. The reason for that is that we are using dumping data to JSON which is not very human readable. Also JSON in golang by default will serialize all the fields even if they are empty (SeeHash
field in the example).Possible improvements:
omitempty
tag to all JSON fields.Why is this needed?
Make reports easier to read
/cc @nwnt @henrybear327
The text was updated successfully, but these errors were encountered: