Right now the monitoring and diagnostics console shows the CPU and RAM measures of all the nodes. However, those are not the only parameters that can strain the nodes. The most common, yes; but not the only ones. We recently ran into this issue after applying several patches to the OS of our nodes. We turned the node services back on and the console was showing the Status of those nodes as STRAINED. The size of the disk was still acceptable so we could not understand what was happening. We could see the RAM and CPU numbers normal and yet we had that status. We spent a long while trying to figure out where the issue was coming from. The console reports the issue however it does not make intuitive at all to understand why your servers are behaving undesirably. The interesting part is that, programmatically, there is access to the readings; they show in the logs right now. So, I am not sure why they don't shown in the console as well.