Add Monitor Quality documentation (#23138)

* Add info for all categories and add filter image

* Removed duplicate overview paragraph, small fixes

* Add review feedback

* Fix links

* Apply suggestions from code review

Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>

---------

Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>

config/_default/menus/main.en.yaml

@@ -1499,6 +1499,11 @@ menu:
       weight: 7
       parent: alerting
       identifier: monitor_settings
+    - name: Monitor Quality
+      url: monitors/quality/
+      weight: 8
+      parent: alerting
+      identifier: monitor_quality
     - name: Guides
       url: monitors/guide/
       weight: 10

content/en/monitors/downtimes/_index.md

@@ -11,6 +11,9 @@ further_reading:
 - link: "/monitors/guide/scoping_downtimes"
   tag: "Guide"
   text: "Scoping downtimes schedules"
+- link: "/monitors/quality/"
+  tag: "Documentation"
+  text: "View monitors that are muted over an extended period"
 - link: "/monitors/"
   tag: "Documentation"
   text: "Create monitors"

content/en/monitors/quality/_index.md

@@ -0,0 +1,77 @@
+---
+title: Monitor Quality
+kind: Documentation
+disable_toc: false
+further_reading:
+- link: "https://app.datadoghq.com/monitors/quality"
+  tag: "In-app"
+  text: "Datadog Monitor Quality"
+- link: "/monitors/"
+  tag: "Documentation"
+  text: "Learn more about Datadog monitors"
+---
+
+## Overview
+
+The Monitor Quality feature in Datadog identifies common misconfigurations in monitoring setups, such as alerts that have been muted for more than 60 days or monitors lacking designated recipients. It enables teams to maintain alerting standards and prevent critical alerts from being missed. Use Monitor Quality to identify and resolve misconfigured monitors all on the same page.
+
+## 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. 
+
+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:
+- [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)
+
+### 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 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.
+
+See which monitors are not alerting due to downtime misconfigurations and unmute them.
+
+### Monitors are missing recipients
+
+When a monitor sets off an alert or notification, you want the alerts to go to the team or person that can resolve it and take action. If no recipients are added to the [monitor notification][2], you decrease how proactive you can be with your services. Use the Monitor Quality page to review the monitors that are configured without any recipients.
+
+### Missing a delay
+
+Data from cloud integrations (such as AWS, Azure, or Google Cloud) is pulled from the respective APIs with a crawler. These metrics arrive with a delay, which you can account for in your monitor configuration. Monitors with cloud data that do not have an [evaluation delay][3] can alert on false positives.
+
+See all the monitors that are crawling cloud data but are missing the recommended delay. For more information on crawled data, see the [Cloud Metric Delay][4] page.
+
+### Misconfigured notification channels
+
+[`@notifications`][5] allow you to customize your monitors so that alerts are forwarded to integrations, workflows, or Datadog cases. If `@notifications` are misconfigured, the expected alerts are not sent to the appropriate channels.
+
+See which monitors have misconfigured notification channels and edit them as necessary.
+
+### 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. 
+
+### Stuck in alert state
+
+Monitors in an `ALERT` state are indications of an issue in your service that needs your attention. Multiple monitors in a constant `ALERT` state take the focus away from the issues that might actually need your attention. Investigate why these monitors are stuck in an alert state and edit your configuration accordingly.
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /monitors/downtimes/
+[2]: /monitors/notify/
+[3]: /monitors/configuration/?tab=thresholdalert#evaluation-delay
+[4]: /integrations/guide/cloud-metric-delay/
+[5]: /monitors/notify/#notifications
+[6]: /monitors/types/composite/
+[7]: https://app.datadoghq.com/monitors/quality
+[8]: https://app.datadoghq.com/monitors/manage