Which metrics do you watch to know a database is heading for trouble before it actually fails?

What the interviewer is looking for

• This question tests monitoring & capacity planning. Tracks key health metrics and growth trends, and plans storage and compute ahead of need.
• Strong answers: Connections, query latency, slow queries, locks, replication lag, cache hit rate, disk space and input output, CPU and memory, and backup success.
• Likely follow-up: Which of those would you alert on, and at what point?

Another way it may be asked: If you could only look at a handful of graphs each morning, which would tell you your database is getting sick?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• Storage on the main database is growing faster than expected. How would you plan for the next year?
• What is the difference between a full, an incremental and a point-in-time backup, and when would you need point-in-time recovery?
• What is an index, and why can adding too many indexes to a table actually hurt?
• A developer asks for full admin access to the production database to debug an issue. How do you respond?
• A query that used to take a second now takes a minute. Walk me through how you would figure out why.

Browse all questions