How do we find out what is causing a high queue for WMITask - This collector only has 95 hosts registered against it and is dedicated (no other services running on it). The WMITask queue length sits between 1500-2000 tasks in the queue.
Is is causing the graphs to show breaks in them. Any help would be great.
Thanks
We dont make this easy to determine - Ill open some enhancement requests now.rnBut, in this case, there are two issues:rn- there is a dead host being monitored by that collector - TWM... Each thread has to timeout for each of the things being collected on that host. Deleting it will help things a bit.rn- the bigger issue is that you have the wmi.user and wmi.pass properties set on all the hosts monitored by this collector. This means that the collector has to check its authentication every single time, for every request for every host. Its much faster if you run the collector services as a domain account, and do not set wmi.user/wmi.pass. Removes several windows authentication steps..
I have removed the dead host and removed the wmi.user and wmi.pass. This made a difference when first done but returned to above 100, which is still causing issues with the graphing. From the attached graph the WMITasks dropped when I made the changes however it has gone backup. Is there anything we can do to find out what is causing it. None of our other customers are having this issue.
