Database Monitoring Checklist
Know what to watch for a production database.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Create a monitoring checklist for [DATABASE_TYPE] in production. Workload type (read-heavy, write-heavy, analytics): [WORKLOAD]. Hosting (managed, self-hosted): [HOSTING]. Biggest past database problem: [PAST_PROBLEM]. List signals grouped as availability, performance, capacity, replication or backup health, and security. For each give the metric, a normal range to be established from my baseline (do not invent numbers), an alert condition, and the action when it fires. Include slow query review, lock waits, connection saturation, storage growth with time-to-full, replication lag, and backup restore tests. Present as a table. Add a weekly review routine and a first-30-days baseline plan. Mark any engine-specific commands as needing verification against current documentation. Add a section describing how to build baselines in the first 30 days, including which times of day and which business events to record, and a short list of five alerts to enable first because they catch the most serious problems. Explain how to avoid alerting on single spikes by using duration conditions, and who should review database alerts monthly.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.