---
title: Database Monitoring Monitor
description: >-
  Create Database Monitoring monitors to alert on query performance, waiting
  queries, and significant changes in explain-plan cost.
breadcrumbs: Docs > Monitors > Monitor Types > Database Monitoring Monitor
---

# Database Monitoring Monitor

## Overview{% #overview %}

With the [Database Monitoring (DBM)](https://docs.datadoghq.com/database_monitoring.md) monitor type, you can create monitors and alert on the data surfaced in DBM. These monitors can be configured to alert you when a DBM event type deviates from a predefined threshold over a given period of time.

Common monitoring scenarios include

- Number of waiting queries
- Number of queries exceeding a given duration
- Significant changes in explain-plan cost

For step-by-step instructions, see Example monitors.

## Monitor creation{% #monitor-creation %}

To create a new DBM monitor in Datadog, navigate to [**Monitors** > **New Monitor** > **Database Monitoring**](https://app.datadoghq.com/monitors/create/database-monitoring) in the UI.

{% alert level="info" %}
There is a default limit of 1000 DBM monitors per account. If you are encountering this limit, consider using [multi alerts](https://docs.datadoghq.com/monitors/configuration.md?tab=thresholdalert#multi-alert), or [Contact Support](https://docs.datadoghq.com/help/) to lift this limit for your account.
{% /alert %}

## Define the search query{% #define-the-search-query %}

Note: As your query changes, the chart above the search bar updates in response.

### Common monitor types{% #common-monitor-types %}

If you don't wish to create your monitor from scratch, you can use one of the following pre-defined monitor types:

- Waiting Queries
- Long Running Queries

{% image
   source="https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/dbm_common_monitor_types.fa8276a84f5b81896bd299cad98e1fef.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/dbm_common_monitor_types.fa8276a84f5b81896bd299cad98e1fef.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example OOTB monitors related to waiting queries and long running queries" /%}

Any feedback on these existing monitor types and other ones you would like to see should be shared with your Customer Success Manager or the [Support Team](https://docs.datadoghq.com/help/).

### Creating monitors from scratch{% #creating-monitors-from-scratch %}

1. Determine whether you want to monitor **Query Samples** or **Explain Plans** and select the corresponding option from the dropdown menu.

{% image
   source="https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/dbm_event_monitor_data_types.9e7f9479e8b625453cb91ae930bbb807.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/dbm_event_monitor_data_types.9e7f9479e8b625453cb91ae930bbb807.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="A dropdown menu showing the different data sources available for the Database Monitoring monitor type" /%}
Construct a search query using the same logic as in the [DBM Query Samples](https://docs.datadoghq.com/database_monitoring/query_samples.md) activity and explain plan explorer. This means that you should select one or more **facets** to include in the search bar. For example, if you wanted to alert on the waiting queries executed by user `postgresadmin`, then your search bar would look like this:
{% image
   source="https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/dbm_example_query_no_group_by.033bf57973a99a21f2a06ad1764e403f.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/dbm_example_query_no_group_by.033bf57973a99a21f2a06ad1764e403f.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="An example search query containing two facets in the search bar." /%}

Note: The monitor you configure alerts over the **unique value count** of the facets.
You also have the option to group DBM events by multiple dimensions. All DBM events matching the query are grouped together based on the values of up to **four facets**. With the group by functionality, you also have the ability to configure the **alerting grouping strategy**:
- **Simple Alert**: Simple Alerts aggregate over all reporting sources, so one alert triggers when one or multiple groups values breach the threshold. You may use this strategy to reduce notification noise.
- **Multi Alert**: Multi Alerts apply the alert to each source according to your group parameters, meaning that an alerting event is generated for each group that meets the set conditions. For example, you can group a query by `@db.user` and select the Multi Alert Aggregation type to receive a separate alert for each database user that triggers the alert as you've defined it.

### Set alert conditions{% #set-alert-conditions %}

1. Set an alert to trigger whenever a query result is `above`, `above or equal to`, `below`, or `below or equal to` a threshold that you define. For help configuring the options in this view, see [Configure Monitors](https://docs.datadoghq.com/monitors/configuration.md?tab=thresholdalert#thresholds).
1. Determine your desired behavior for when data is missing for 5 minutes, for example, `evaluate as zero`, `show NO DATA`, `show NO DATA and notify`, or `show OK`.

#### No data and below alerts{% #no-data-and-below-alerts %}

To receive a notification when an application has stopped sending DBM events, set the condition to `below 1`. This alert triggers when no DBM events match the monitor query in a given time frame across all aggregate groups.

When you split the monitor by any dimension (tag or facet) and use a `below` condition, the alert is triggered **if and only if**:

1. There are DBM events for a given group, but the count is below the threshold.
1. There are no DBM events for any of the groups.

#### Advanced alert conditions{% #advanced-alert-conditions %}

For more information about advanced alert options such as evaluation delay, see [Configure Monitors](https://docs.datadoghq.com/monitors/create/configuration.md#advanced-alert-conditions).

### Notifications{% #notifications %}

For more information about the **Configure notifications and automations** section, see [Notifications](https://docs.datadoghq.com/monitors/notify.md).

## Example monitors{% #example-monitors %}

### Number of waiting queries{% #number-of-waiting-queries %}

This monitor detects whether the number of waiting queries has exceeded a given threshold.

{% image
   source="https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/waiting_queries_monitor.b28cfd6a90d8a906eef9ca57614b3f5f.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/waiting_queries_monitor.b28cfd6a90d8a906eef9ca57614b3f5f.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="A configured metrics query for monitoring the number of waiting database queries" /%}

#### Build the monitoring query{% #build-the-monitoring-query %}

1. In Datadog, go to [**Monitors > New Monitor > Database Monitoring**](https://app.datadoghq.com/monitors/create/database-monitoring).
1. In the **Common monitor types** box, click **Waiting Queries**.

#### Set the alert threshold{% #set-the-alert-threshold %}

1. To gain context on the range of typical values, set the time frame to **Past 1 Month** using the dropdown menu at the top of the chart.
1. Enter your chosen alerting threshold value in the **Alert threshold** box. For example, if the number of waiting queries stays below `3000` on the chart, you might set **Alert threshold** to `4000` to represent unusual activity. For configuration details, see [Set alert conditions](https://docs.datadoghq.com/monitors/configuration.md?tab=thresholdalert#set-alert-conditions) and [Advanced alert conditions](https://docs.datadoghq.com/monitors/create/configuration.md#advanced-alert-conditions).
1. Use the red shaded area on the chart to verify that your alert won't trigger too rarely or too often, and adjust the threshold value as needed.

#### Configure notifications{% #configure-notifications %}

1. Under **Configure notifications and automations**, write the notification message. For detailed instructions, see [Notifications](https://docs.datadoghq.com/monitors/notify.md). You can use this text for the message body:
   ```text
   {{#is_alert}}
   Waiting queries on {{host.name}} have exceeded {{threshold}} 
   with a value of {{value}}.
   {{/is_alert}}
   
   {{#is_recovery}}
   The number of waiting queries on {{host.name}}, which exceeded {{threshold}},
   has recovered.
   {{/is_recovery}}
```
1. Add yourself to the notification recipients by typing and then selecting your name in the **Notify your services and your team members** box.

#### Verify and save the monitor{% #verify-and-save-the-monitor %}

1. To verify the monitor setup, click **Test Notifications**. Trigger a test alert by choosing **Alert**, then click **Run Test**.
1. Click **Create** to save the monitor.

### Queries exceeding 30 seconds{% #queries-exceeding-30-seconds %}

This monitor detects whether the number of long-running queries has exceeded a given threshold.

{% image
   source="https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/long_running_queries_monitor.2bd5c72c246bb333d6f81a25cd5d4ca7.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/long_running_queries_monitor.2bd5c72c246bb333d6f81a25cd5d4ca7.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="A configured metrics query for monitoring the number of long-running database queries" /%}

#### Build the monitoring query{% #build-the-monitoring-query-1 %}

1. In Datadog, go to [**Monitors > New Monitor > Database Monitoring**](https://app.datadoghq.com/monitors/create/database-monitoring).
1. In **Common monitor types**, click **Long Running Queries**.
1. Update the query filter to **Duration:>30s**.

#### Set the alert threshold{% #set-the-alert-threshold-1 %}

1. To gain context on the range of typical values, set the time frame to **Past 1 Month** using the dropdown menu at the top of the chart.
1. Enter your chosen alerting threshold value in the **Alert threshold** box. For example, if the values on the chart stay below `2000`, you might set **Alert threshold** to `2500` to represent unusual activity. For configuration details, see [Set alert conditions](https://docs.datadoghq.com/monitors/configuration.md?tab=thresholdalert#set-alert-conditions) and [Advanced alert conditions](https://docs.datadoghq.com/monitors/create/configuration.md#advanced-alert-conditions).
1. Use the red shaded area on the chart to verify that your alert won't trigger too rarely or too often, and adjust the threshold value as needed.

#### Configure notifications{% #configure-notifications-1 %}

1. Under **Configure notifications and automations**, write the notification message. For detailed instructions, see [Notifications](https://docs.datadoghq.com/monitors/notify.md). You can use this text for the message body:
   ```text
   {{#is_alert}}
   The number of queries with a duration of >30s has exceeded 
   {{threshold}} on {{host.name}} with a value of {{value}}.
   {{/is_alert}}
   
   {{#is_recovery}}
   The number of queries with a duration of >30s on {{host.name}}, 
   which exceeded {{threshold}}, has recovered.
   {{/is_recovery}}
```
1. Add yourself to the notification recipients by typing and then selecting your name in the **Notify your services and your team members** box.

#### Verify and save the monitor{% #verify-and-save-the-monitor-1 %}

1. To verify the monitor setup, click **Test Notifications**. Trigger a test alert by choosing **Alert**, then click **Run Test**.
1. Click **Create** to save the monitor.

### Change in explain-plan cost{% #change-in-explain-plan-cost %}

{% image
   source="https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/explain_plan_cost_monitor.686f4b16d3af98cebb52ae6d5d421282.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/database_monitoring/dbm_event_monitor/explain_plan_cost_monitor.686f4b16d3af98cebb52ae6d5d421282.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="A monitor configured to track changes in average daily explain-plan cost" /%}

This monitor detects a significant change in daily average explain-plan cost by comparing the results of two queries:

- Query **a** reflects the current explain-plan cost
- Query **b** reflects the explain-plan cost a week ago

This allows the comparison of two consecutive Mondays, for example.

With minor changes, the monitor can instead reflect hourly averages, measure the difference between today and yesterday, group by query signature instead of host, and so on.

#### Build the first monitoring query{% #build-the-first-monitoring-query %}

1. In Datadog, go to [**Monitors > New Monitor > Database Monitoring**](https://app.datadoghq.com/monitors/create/database-monitoring).
1. Under **Define the search query**, make the following updates:
   - Change **Query Samples** to **Explain Plans**.
   - Change **\*** to **Explain Plan Cost (@db.plan.cost)**. Typing "cost" into the field populates the autocomplete options.
   - Change **(everything)** to **Host (host)**.
1. Click the **∑** button and type **rollup** to populate the autocomplete suggestions. Choose **moving\_rollup**.

#### Build the second monitoring query{% #build-the-second-monitoring-query %}

1. Click **Add Query** to create query **b**, a copy of query **a**.
1. Change **a + b** to **a - b**. Because the two queries are temporarily identical, this value displays on the chart as 0.
1. In the **b** query, click the **∑** button and choose **Timeshift > Week before**. This configures the monitor to detect significant changes between last week and the present.

#### Set the alert threshold{% #set-the-alert-threshold-2 %}

1. In the dropdown menu at the top of the chart, expand the time frame to **Past 1 Month** to gain context on the typical cost variation from week to week.
1. Enter your chosen alerting threshold value in the **alert threshold** box. For example, if the difference in explain-plan cost stays below `8000` on the chart, you might set **alert threshold** to `9000` to represent unusual activity. For configuration details, see [Set alert conditions](https://docs.datadoghq.com/monitors/configuration.md?tab=thresholdalert#set-alert-conditions) and [Advanced alert conditions](https://docs.datadoghq.com/monitors/create/configuration.md#advanced-alert-conditions).
1. Use the red shaded area on the chart to verify that your alert won't trigger too rarely or too often, and adjust the threshold value as needed.

#### Configure notifications{% #configure-notifications-2 %}

1. Under **Configure notifications and automations**, write the notification message. For detailed instructions, see [Notifications](https://docs.datadoghq.com/monitors/notify.md). You can use this text for the message body:
   ```text
   {{#is_alert}}
   The daily average explain-plan cost on {{host.name}} has increased by at least {{threshold}} 
   versus one week ago, with a value of {{value}}.
   {{/is_alert}}
   
   {{#is_recovery}}
   The daily average explain-plan cost on {{host.name}} has recovered to within {{threshold}}
   of the cost on this day last week.
   {{/is_recovery}}
```
1. Add yourself to the notification recipients by typing and then selecting your name in the **Notify your services and your team members** box.

#### Verify and save the monitor{% #verify-and-save-the-monitor-2 %}

1. To verify the monitor setup, click **Test Notifications**. Trigger a test alert by choosing **Alert**, then click **Run Test**.
1. Click **Create** to save the monitor.