Yeah I was thinking something like this too, hopefully someone makes this if it hasn't been already. If the diagrams had some linkage to your code you'd be abl

Yeah I was thinking something like this too, hopefully someone makes this if it hasn't been already. If the diagrams had some linkage to your code you'd be able to see what a failed unit test means in the overall context of the app, what code is used in which block, what protocol is used for connections between blocks, a summary of what each block does etc... A monitoring tool as you say - and since you'll use it often you'll probably keep it up to date