Skip to content

Add section on noisy monitors to Monitor Quality #30318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 8, 2025
Merged

Add section on noisy monitors to Monitor Quality #30318

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions content/en/monitors/quality/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,22 +16,27 @@ The Monitor Quality feature in Datadog identifies common misconfigurations in mo

## View misconfigured monitors

From the [**Manage Monitors**][8] page, click the [**Monitor Quality**][7] tab to access a list of monitors that need improvement. Datadog automatically enables this feature after you create your first monitor.
From the [**Manage Monitors**][8] page, click the [**Monitor Quality**][7] tab to access a list of monitors that need improvement. Datadog automatically enables this feature after you create your first monitor.

Filter and view the [Monitor Quality page][7] based on the teams, creators, services, or environments to organize and manage the list.
Filter and view the [Monitor Quality page][7] based on the teams, creators, services, or environments to organize and manage the list.

{{< img src="monitors/quality/filter_monitor_quality.png" alt="Filtering dropdown options for creators, teams, services, and env available on the Monitor Quality page" style="width:100%;" >}}

## Improve monitors and follow best practices

Monitor Quality displays your monitors with the following quality issues:
- [High volume of alerts](#high-volume-of-alerts)
- [Muted for over 60 days](#muted-for-over-60-days)
- [Missing recipients](#monitors-are-missing-recipients)
- [Missing a delay](#missing-a-delay)
- [Have misconfigured notification channels](#misconfigured-notification-channels)
- [Composite monitors are missing constituents](#composite-monitors-are-missing-constituents)
- [Stuck in an alert state](#stuck-in-alert-state)

### High volume of alerts

Monitors that trigger too frequently can lead to alert fatigue and desensitize teams to important alerts. With the Monitor Quality page, you can identify and fix monitors that are generating a high volume of alerts.

### Muted for over 60 days

[Downtimes][1] are useful for silencing alerts during scheduled maintenance, planned outages or system shutdowns, or to stop alerts during weekends and evenings. However, monitors that have been muted, or partially muted, for an extended period (more than 60 days) may indicate an oversight. You can unmute these monitors to resume alerting and ensure comprehensive monitoring coverage.
Expand All @@ -56,7 +61,7 @@ See which monitors have misconfigured notification channels and edit them as nec

### Composite monitors are missing constituents

[Composite monitors][6] evaluate the combined state of multiple sub monitors (constituents) following user-defined logic. Composite monitors that reference deleted constituents do not evaluate or notify. Identify inactive composite monitors and delete them.
[Composite monitors][6] evaluate the combined state of multiple sub monitors (constituents) following user-defined logic. Composite monitors that reference deleted constituents do not evaluate or notify. Identify inactive composite monitors and delete them.

### Stuck in alert state

Expand Down
Loading