-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The vmware.xml has a bug on VM Processor #61
Comments
Each analysis in PAL must focus on a counter name, therefore \VM Processor(*)* will not work. I good update to the PAL Threshold File Editor would be to add a new analysis for each counter name. But at this point, I would rather completely rewrite PAL than fix this. |
The thing is @clinthuffman , its the collection that's bugged, not the analysis. |
Something seems to have changed in VMWare's perfmon counters. The template was made to collect individually named VM Processor counter objects. I think the name changed at some point on these.
The easy button is to have the data collector change from the individual call-outs to just
as opposed to
It's a lame fix but it's all I have (I don't run vmware here).
The text was updated successfully, but these errors were encountered: