Some or all of the performance counters are not working.
Kaseya has developed a diagnostic process that you can run on affected machines. This app will interrogate the machine and inform you why your monitoring is not working and in most cases how to fix it.
Create the "Managed Files" folder of "MDwhyIsMonitoringNotWorking" within the "Shared" folder.
Upload the attached file "MDwhyIsMonitoringNotWorking.exe" to the above location.
Import the attached Xml which will create an agent procedure with the name of "MDWhyIsMonitoringNotWorking"
When executing this script you'll be presented with this screen that asks you 2 questions
The first question "MonitorsetId Number to Test." Is asking you which monitorset assigned to this machine should be tested against the machine.
You can find this Number from the Assign Monitoring" tab
The box "Email to send results to" Is asking for who should receive the results of the interrogation. (This was done to be compatible with SaaS)
Note:- You can execute this script across multiple machines , assuming they all have the monitorset in question
After running you'll receive a detailed email containing the monitoring debug process.
The debug process and be broken down into two parts
1) The first is machine specific issues.
2) The second part deals with Object, Counter Instance issues for every row in the monitorset.
Windows performance counters only ( not services or processes. ) However some of the issues identified by this application may aslo be the same reason why they don't work too.
To identify machines that have counters that are not responding ( are having issues ) please see the below KB
To redeploy Lua because Lua has been identified at the issue please see this KB
If a result is retuned asking you to run "FixPerfmonCounters_Delete" please see this KB
This application will identify a number of reasons why the monitoring is not working that are not "Kaseya" issues but issues with the machine itself.
I have created this topic for customers to allow customers to share how they have fixed the various "Customer to resolve issues"
XML Version 1
EXE Verison 2.0
Added support for objects with spaces in them.
Re ordered some of the diagnostic steps to better identify the current issue the agent is facing. (less redeploy LUA statements when this is not actually the problem.)
Things stuck in the "events" folder were not being picked up correctly
Added identification of counters that are not out putting their current logs to the agents current Working Dir.