Hey there! Thanks for the comment, I'm glad its been going well. I'll reply to a couple of your points below: > The documentation is good. It's a bit spartan

Hey there! Thanks for the comment, I'm glad its been going well. I'll reply to a couple of your points below: > The documentation is good. It's a bit spartan > for some of the more complex things Yes, I've documented the protocols[1] but I haven't gone into much more detail. The docs may also need some iterating on as/when people try to develop new clients. > Our biggest concern has been with logging. > Message-bus architectures have all the > difficulties of cooperative multitasking, > with the added problem that events can also > go missing. Good logs are invaluable in > debugging this kind of problem. My understanding > is that this is on the roadmap Yep. Two things are on the roadmap that are relevant to this: 1. Revamping the logging system, likely to have an option to support structlog 2. The ability to see a causal trace for each message (Message C was caused as a result of Message B, which was caused by Message A) I think no. 2 should be straightforward, and I think no. 1 is just going to take a grim sense of determination and deleting a bunch of old logging code. [1]: https://lightbus.org/reference/protocols/ https://lightbus.org/reference/protocols/