Custom thresholds not triggering correctly on Windows Database servers

We have a number of database servers that frequently run near 100% utilization for CPU and memory. Because this is a common issue with these, we're not worried about being alerted to it, and I've gone in to each node and set the thresholds to 97% and 99% for Warning and Critical respectively. However, they're STILL showing up in the standard threshold category.

Find more posts tagged with

Accepted answers

kpmarcin

Hello @CHoogerhuis

Could you please check the thresholds directly on the Physical Memory volume? Click on the Physical Memory and then click Edit to check for thresholds:

Please let me know if this will resolve your issue. Thanks.

If you are wondering, why there are two places to modify RAM thresholds, it can be due to monitoring Physical Memory as a separate volume, which you can disable:

All comments

kpmarcin

How long did you wait after the change?
There is a X consecutive polls of 20, so if you poll node statistics every 10 minutes, you would see a change after 200 minutes.

CHoogerhuis

It's been days, if not weeks at this point, depending on the servers.

kpmarcin

Hello @CHoogerhuis

Could you please check the thresholds directly on the Physical Memory volume? Click on the Physical Memory and then click Edit to check for thresholds:

Please let me know if this will resolve your issue. Thanks.

If you are wondering, why there are two places to modify RAM thresholds, it can be due to monitoring Physical Memory as a separate volume, which you can disable:

CHoogerhuis

@kpmarcinThank you! That is EXACTLY what was wrong. Is there a way to change these settings on a group basis, or do I have to enter in to each individual node and then volume to adjust the settings?