Performance Health incorrectly calculates when monitoring an AlwaysOn enivronment
The Performance Health Monitor claims a secondary node is unhealthy because of the wait time for AlwaysOn or MISC events. As the secondary node has no other task than waiting for events from the primary node, it appears the Performance Monitor is calculating a wrong index.
STATUS: Issue fixed in version 12.1. The latest version of Spotlight Enterprise can be downloaded here
This issue is planned to be fixed in the 12.1 release, currently due in Nov 2017.
The calculation of Performance Health will be improved so this bug also number includes other problems when calculating Performance Health.