Health alerts and warning signals in Databases app
- Latest Dynatrace
- Explanation
- Published Jul 07, 2026
- Preview
Database health alerts and warning signals in 
Databases detect and categorize availability, performance, configuration, and resource issues in monitored database instances, with critical alerts triggering Dynatrace problems and warnings indicating early degradation. Those are grouped into categories, use predefined templates for alerting, and contribute to a unified health score for quick assessment and troubleshooting.
Overview
Database health alerts and warning signals are predefined anomaly-based events in Databases that identify availability, performance, configuration, and resource-usage issues in monitored database instances. For details, see Health alerts and warning signals.
- Health alerts (critical): Indicate conditions that require action, trigger a Dynatrace problem, and start root cause analysis.
- Warning signals (noncritical): Indicate early signs of degradation that should be addressed proactively and may escalate to critical issues if ignored.
Database Monitoring provides default health alert and warning signals categories. These categories are automatically generated for PostgreSQL and MySQL when the Database Monitoring license is enabled. It also includes pre-defined templates for availability, performance degradation, and database growth scenarios.
Categories of health alert and warning signals
Database-related warning signals and health alerts cover multiple aspects of database behavior:
- Queries: You can detect inefficient, slow, or high-cost queries, abnormal execution patterns, or increased query load that can indicate query-level performance bottlenecks.
- Schema: You can detect structural or configuration issues such as missing indexes, inadequate schema design, or growth‑related risks that impact performance and scalability.
- DB instance activity: You can monitor infrastructure-level conditions, such as CPU, memory pressure, connections, and availability, that affect database stability.
- Database activity: You can capture workload patterns, such as throughput, transaction rates, and data growth anomalies, that indicate changes in database behavior.
Available alert templates
A health alert template in Databases creates an alert that triggers a Dynatrace problem when the template's conditions are met. There are three predefined alert templates:
- Availability: Detects when a database instance is unreachable, has stopped unexpectedly, or is not responding.
- Performance drop: Detects when a low percentage of data requests are served from memory, forcing frequent slow disk reads. This indicates memory pressure or inefficient queries.
- Database size: Detects when the database has grown large enough to risk slower queries, higher costs, or storage issues, indicating a need for optimization or scaling.
These templates are supported across Dynatrace database vendors monitored by Databases.
Create an alert from a template
You can configure predefined health alerts and warning signals through the Alert templates tab.
To create an alert from a template
- Open the Alert templates tab.
- Select a database vendor and expand the section to see the available templates.
- Select New Alert and fill in the required details.
- Select Create.
You can customize the alert in the Anomaly Detection app or accept the defaults to create it immediately. For custom alert configuration, see Create a simple anomaly detector.
Contribution to the health score
The health score gives a single, aggregated view of a database’s overall condition by combining multiple health checks and anomaly detections.
- Warning signals and health alerts highlight individual issues and early indicators.
- Health score brings these signals together into an easy‑to‑read measure of the database’s current state and trend.
This allows you to:
- Assess if a database is healthy, degrading, or critical, without analyzing each signal separately.
- Drill down into underlying warning signals and alerts for detailed investigation.
For details about health score calculation, see Database health score overview.
Databases