At the moment there appear to be "dangling sessions" in the orchestrator (which are partially to blame for #1), but there is no way to see this.
We need some sort of introspection.
A simple implementation might be to have a dump command that will serialise all internal data structures as one big JSON object (while catering for references between objects not causing an infinitely large data structure), and allow that command to be used even when not logged in. Then a simple toplevel script (like logreader) would do the trick.
At the moment there appear to be "dangling sessions" in the orchestrator (which are partially to blame for #1), but there is no way to see this.
We need some sort of introspection.
A simple implementation might be to have a
dumpcommand that will serialise all internal data structures as one big JSON object (while catering for references between objects not causing an infinitely large data structure), and allow that command to be used even when not logged in. Then a simple toplevel script (likelogreader) would do the trick.But there may be better ways to do this.