From 12ca0d6928cf05e46b9c28f197443536bec9dfb2 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Fri, 7 Aug 2026 15:38:42 +0000 Subject: [PATCH] docs(monitors): Clarify metric monitor intervals Co-Authored-By: Nick Meisenheimer --- docs/product/monitors-and-alerts/monitors/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/product/monitors-and-alerts/monitors/index.mdx b/docs/product/monitors-and-alerts/monitors/index.mdx index 75650cf054c6b..2cbf71c24e721 100644 --- a/docs/product/monitors-and-alerts/monitors/index.mdx +++ b/docs/product/monitors-and-alerts/monitors/index.mdx @@ -59,7 +59,7 @@ Assignees set by [ownership rules](/product/issues/ownership-rules/) will overri Metric Monitors are used to track thresholds on data from errors, spans, logs, releases, and application metrics. -Choose the dataset and metric, the interval for how often to check, and the way you want to monitor for changes. You can choose an absolute number threshold, a percentage change, or dynamic anomaly detection. +Choose the dataset and metric, the interval over which to aggregate data, and how you want to monitor for changes. You can choose an absolute number threshold, a percentage change, or dynamic anomaly detection. For percentage change monitors, the interval sets the duration of both the current and comparison periods. Longer intervals include more data and may be evaluated less frequently. #### Issue Detection Settings