Does anybody rely upon the resource monitoring feature in the Thermos observer UI (the UI on port :1338)? Specifically the cpu/ram/disk columns.
As far as I know, nobody is using Thermos in the absence of Mesos, and because the Mesos slave provides the same information more accurately, I'm inclined to remove this feature from the UI. This will simplify the code quite a bit and also reduce the resources consumed by the observer as well (we find it burns 2-4% CPU per box in practice.) ~brian
