You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To ensure the Health Monitor is robust, we should add additional checks to ascertain health:
Key endpoints are responding (we already have this in the form of a search endpoint test)
Measure response times of search endpoint -- if latency is high, that's an issue
CPU, Memory Usage, Disk Space, and IO/Rates of Client VM and Database VM -- if these go over (and possibly under) certain limits, that's worth warning about.
Backend database is online and responding to simple queries
In addition, we want to be careful not to add too much clutter -- if the Backup Database is offline, then obviously CPU, Memory Usage, and other tests will fail as well, so we don't need all of those alerts firing off at once, and some should be suppressed if others are run.
In addition to adding these checks, we should then create tests to validate that these perform as expected.
The text was updated successfully, but these errors were encountered:
To ensure the Health Monitor is robust, we should add additional checks to ascertain health:
In addition, we want to be careful not to add too much clutter -- if the Backup Database is offline, then obviously CPU, Memory Usage, and other tests will fail as well, so we don't need all of those alerts firing off at once, and some should be suppressed if others are run.
In addition to adding these checks, we should then create tests to validate that these perform as expected.
The text was updated successfully, but these errors were encountered: