Monitor database metrics together: request latency, throughput, waits, resource use, capacity and recoverability. Compare each with a baseline for the same workload.
Which numbers explain a slowdown?
Start with the user-facing symptom, such as slower checkout queries. Compare request volume and execution times with CPU, disk latency, blocking and waits during the same interval. A busy CPU during a normal batch run may be expected; rising latency at normal traffic needs investigation.
What belongs in an actionable alert?
Define the sustained condition, the affected workload and the person who can respond. Pair disk growth with time to capacity, replication lag with recovery objectives, and backup age with the latest successful restore test.
Where can I learn more about database monitoring metrics?
Further reading: Microsoft’s guide to monitoring SQL Server performance.
Related Solvaria FAQ: What is a database monitoring system?
Where can I find documentation and support for database monitoring metrics?
Consult Microsoft database monitoring and performance guidance for product behavior and implementation guidance. Match the documentation to your deployed version and test changes before production use.
For help applying this to your environment, explore Solvaria’s database monitoring metrics support resources or contact our team.
Related FAQ: How can proactive strategies support database performance?.