Open JedWatson opened 10 years ago
I'm unsure on that myself. I generally log tickets against the project they actually apply to. The idea is that all these things are decoupled enough that any one of them can be replaced/duplicated and it will be fine. It might make the whole ecosystem more approachable if there was a single place for issues, though.
The logging process has been designed with that use case in mind, so this is definitely do-able without any rethinking/refactoring. Just a matter of plumbing it all up.
Sorry if this is in the wrong repo; not sure if you'd like to generally collect FM ideas here or in each component's repo.
It'd be great to stream process logs to the QM UI rather than having to curl
/monitor
on each cavalry slave.I'm imagining a UI where you can filter by slave / process / both slave + process / message text and by default see a consolidated view across the cluster.