Skip to content
Open
Changes from all commits
Commits
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
5 changes: 1 addition & 4 deletions docs/product/new-monitors-and-alerts/monitors/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kcons can you confirm Replay issues note here is correct?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's correct.

- **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)
Expand Down
Loading