From faf871c4d05bb63fe2dc097c46f73717c7d5c06c Mon Sep 17 00:00:00 2001
From: Nicholas Meisenheimer <76002357+souredoutlook@users.noreply.github.com>
Date: Tue, 31 Mar 2026 08:59:18 -0400
Subject: [PATCH] clarify default monitors block

---
 docs/product/new-monitors-and-alerts/monitors/index.mdx | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/docs/product/new-monitors-and-alerts/monitors/index.mdx b/docs/product/new-monitors-and-alerts/monitors/index.mdx
index 16d1134b4904a6..daa471cafb1937 100644
--- a/docs/product/new-monitors-and-alerts/monitors/index.mdx
+++ b/docs/product/new-monitors-and-alerts/monitors/index.mdx
@@ -24,11 +24,8 @@ You can use Custom Monitors to track errors based on span attributes and custom
 
 Sentry also provides default monitors that are automatically created for you when you create a new project.
 
-- **Issue Stream Monitor**: The default monitor tracking new issues of all types created for a project
+- **Issue Stream Monitor**: The default monitor tracking new issues of all types created for a project, including issue types that may not have a dedicated Monitor detecting them (ex. Replay issues)
 - **Error Monitor**: The default monitor based on [issue grouping/fingerprint rules](/concepts/data-management/event-grouping/)
-- **Replay Monitor**: Once you've configured [Session Replay](/product/explore/session-replay/), issues will be created via the Replay Monitor
-- **Trace Monitor**: Once you've configured [Tracing](/product/tracing/), issues will be created via the Trace Monitor
-- **Profile Monitor**: Once  you've configured [Profiling](/product/explore/profiling/), issues will be created via the Profile Monitor
 
 ## Creating a Monitor
 ![create-monitor =800x](./img/create-monitor.png)