Thanks for the note and the link! We'll get this fixed in the next code release and include a helpful link to the TechNet website for people who want to research available performance counters that can be monitored.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
I've noticed in the 1.2B release notes it says this is fixed.
- Fixed bug in example Logon Errors performance counter in Windows server wizard
This does not appear to be the case in 1.2C and D. Well I couldn't get the Wizard to create a service in 1.2C (due to a bug) and in 1.2D the service is created as follows:
$ARG3$ = -l "\\Server\\Errors System","Login Errors since last reboot is %.f" -w 2 -c 20
And also in the wizard itself it has the performance counter field populated with \\Server\\Errors System
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.