The Alerts page helps teams review and triage conditions detected by Mini DBA across monitored database servers. It is the main console page for understanding what currently needs attention.
What Alerts Are For
Alerts help identify problems such as availability issues, health check failures, performance thresholds, failed monitoring checks, capacity concerns, and platform-specific conditions.
Use alerts to move from "something is wrong" to the affected engine, server, database, metric, or query area.
Alert Workflow
- Open Alerts.
- Filter or sort by severity, server, database platform, status, or time.
- Review the alert message and affected object.
- Open the related server page from the navigation tree.
- Use activity, waits, queries, memory, files, logs, or health check pages to investigate.
- Confirm notification routing in alert recipients, recipient groups, and integration settings.
Alert Scope In MSP Mode
In MSP mode, alert scope depends on where you are in the console.
Use the global Alerts page Current tab when you want active alerts from all connected engines and all monitored servers. This is the estate-wide live triage view and is the best place to answer "what is alerting right now?"
Use the current selected engine context when you want to focus on one customer, site, or engine estate. Select the engine, then use the navigation tree and server-specific Alerts pages. In MSP mode, the navigation tree is filtered to the selected engine. Server-specific Alerts pages show current, uncleared, history, configure, and maintenance-window information for that server.
The global Alerts page Uncleared and History tabs are loaded through the current selected engine service. To review another engine's uncleared or historical alerts, switch to that engine and refresh the tab.
| Need | Where To Go |
|---|---|
| Current active alerts across all engines | Global Alerts, Current tab |
| Current active alerts for one selected engine | Select the engine, then use its server tree and server-specific Alerts pages |
| Uncleared or historical alerts for the selected engine | Global Alerts, Uncleared or History tab |
| Alerts for one monitored server | The server's Alerts page |
| Alert thresholds, copy/import/export, and maintenance windows | The server's Alerts page, Configure, Copy Config, and Maintenance Windows tabs |
Copy, Export, And Import Alert Configuration
Use Copy, Export, And Import Alert Configuration when you need to reuse alert policies across same-type servers or move alert configuration between Mini DBA Engine instances. The server Alerts page Configure tab includes Copy Config, which can copy from another monitored server into the current server, copy the current server to selected target servers, copy between connected engines in MSP mode, or import from an exported trigger file.
Copying alert configuration overwrites the target server's current alert thresholds and notification settings. Review recipients, recipient groups, custom alert SQL, maintenance windows, and customer-specific routing before applying a copied policy broadly.
Custom Alerts
Use Custom Alerts when a monitored server needs a user-defined query alert that is not covered by the built-in Mini DBA alert catalog. Custom alerts are created from a server's Alerts page and can use Boolean, Numeric, or Result Set query return types.
Custom alerts are useful for local business rules, application queues, customer-specific service indicators, or temporary incident checks. They still follow the normal Mini DBA alert workflow, so review routing, thresholds, descriptions, and ownership before sending them to notification channels.
Use Alert Triage With AI when you want Mini DBA AI Assistant to summarize active alerts, group related symptoms, and create an investigation plan from alert, metric, and session context.
Notification Setup
For alerts to reach people outside the console, configure:
- Email server settings
- Alert recipients
- Recipient groups
- Slack integration
- Microsoft Teams integration
- PagerDuty integration
- Jira integration
Troubleshooting Missing Alerts
- Confirm the server is licensed and actively monitored.
- Confirm the engine is connected in Settings.
- Check Service Log for sampling or alert-processing errors.
- Confirm recipients and integrations are enabled.
- Confirm the relevant alert rule or health check is active.
Alert Triage Tips
Triage alerts by severity, business impact, and recency. A new warning on a critical production server can matter more than an older high-severity alert on a test system. When multiple alerts fire together, look for the earliest meaningful signal and the shared engine, server, database, or workload.
Alerts should lead to a next action: investigate, escalate, suppress by policy, tune the threshold, or document acceptance. Repeating alerts are especially important because they either show an unresolved problem or a threshold that no longer matches the environment.
Alerts FAQ
Are alerts the same as root cause?
No. Alerts identify conditions. Use the related monitoring pages to diagnose cause and impact.
Why are alerts missing from notifications?
Check alert routing, recipient availability, integration settings, service logs, and whether the alert severity is configured for that channel.
Should I clear alerts manually?
Follow your team's process. Confirm the condition has recovered and document any action taken.
How do I see alerts from every MSP engine?
Open the global Alerts page and use the Current tab for active alerts across all connected engines. Use Enterprise View for a dashboard-style cross-engine health view.
How do I focus on one selected engine?
Select the engine you want to investigate, then use the filtered navigation tree and server-specific Alerts pages. For uncleared and historical alerts, switch to the engine and refresh the global Alerts tab.
Related Pages
- Mini DBA MSP Mode
- Enterprise View
- Reports
- Custom Alerts
- Copy, Export, And Import Alert Configuration
- Alert Triage With AI
- SQL Server alerts
- Azure SQL alerts
- PostgreSQL alerts