QoE sounds neat but what 'exactly' does it do and what are the 'best practices' to deploy to get the most out of it?
Thanks!
I use QoE to display NPM information in new ways that show relationships between resources that create experiences for users. For example, it's easy to monitor NPM servers and their SQL resources with QoE, and then see how their resources rank and change as activity on them changes. When NPM seems slow, QoE shows the items supporting NPM's functionality that are not within expected thresholds.
That goes for everything that QoE monitors. Just enabling it and installing it with WMI on a bunch of servers will likely show you things on those servers you may have been missing. And when folks talk about performance dissatisfaction for apps on those servers, QoE will likely show them at the top of the problem list for whatever is taking longer than is nominal.
