The few items you called out are because the rows of the view are populated based on ANY of the pillars being true, as in cpu could be stressed, mem could be stressed, or net could be stressed. If any of those are true, it has to give recommendations for all pillars. In terms of the stress report, it would be expected that a "stress" report would give recommendations that include more resources than are already allocated. Other items that recommend 'less' resources then required, aren't the trigger for inclusion in to this report. If the recommendation was 'less' than what is currently allocated, that wouldn't be undersized/stressed, that would be OVERSIZED, Again, you need to consider how the report was built. If you want a report where 'ONLY' objects that appear are fully accurate, split the view in to separate views for specifically Memory, then another for CPU, then another for network, since that is the only way that every single field would be technically 'stressed'. Make sense?
↧