Is there a way, when logging in JSON, to get a readable connection summary log. When logging in JSON the log is unusable and the tables included in the log do not get populated. I like the log because it gives a great overview of the sensors.
since trace-summary (the tool that generates the connection summaries)
only supports the standard Bro log file syntax, there currently is no way
to get a usable output when only logging in json.
You could log in json and in the standard format simultaneously, as one
solution. Adding json support to trace-summary also should not be that
hard - but I don't think that that is currently on anyones plate.