Baseline value above 100%

The fact that you have baselines calculated over 100%, then this server has been running very HOT.  The details on how these are calculated are detailed on the support site.

Thanks KMSigma.SWI but how can I alert on this, if alert is set to trigger for critical value, current value would always <=100%, while threshold is set above 100%

You can't use the ${USE_BASELINE_WARNING} or ${USE_BASELINE_CRITICAL} macros.  You'd have to statically define those (say as 85% and 90%).

I think you might be confusing what this change does.  It says that "For this specific node, I want it to be considered 'critical' when it's over 90%."  Ergo, what is considered critical is defined by this setting.

I try to never use a single polling entry to define warning or critical.  I much prefer the last X of Y option (say 3 of 5 polls) because a CPU can easily spike to over 90% for a very brief moment, but it's only really a 'problem' if it's happened over some time frame.

You can't use the ${USE_BASELINE_WARNING} or ${USE_BASELINE_CRITICAL} macros.  You'd have to statically define those (say as 85% and 90%).

I think you might be confusing what this change does.  It says that "For this specific node, I want it to be considered 'critical' when it's over 90%."  Ergo, what is considered critical is defined by this setting.

I try to never use a single polling entry to define warning or critical.  I much prefer the last X of Y option (say 3 of 5 polls) because a CPU can easily spike to over 90% for a very brief moment, but it's only really a 'problem' if it's happened over some time frame.

Thank you KMSigma.SWI

How would you turn this off for vm's not need in your environment ? 

You can edit the thresholds in the screenshot above and untick the checkboxes on the left hand side next to Warning and Critical. You'll still collect the data but the node won't go warning or critical if they're unticked.