fix(monitors): Update tour carousel copy to clarify issue creation#113169
Open
souredoutlook wants to merge 1 commit intomasterfrom
Open
fix(monitors): Update tour carousel copy to clarify issue creation#113169souredoutlook wants to merge 1 commit intomasterfrom
souredoutlook wants to merge 1 commit intomasterfrom
Conversation
Rewrites steps 3 and 4 of the monitors onboarding carousel to more clearly explain that Monitors create Issues, and that Alerts notify teams about those Issues. Previous copy was vague about the role of issue creation in the monitor-to-alert flow. - Step 3 title: 'Alerts notify your team' → 'Alerts notify your team of issues' - Step 3 body: clarifies that issues created by Monitors trigger Alerts - Step 4 body: reframes connecting Alerts around issue notification routing Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Frontend
malwilley
approved these changes
Apr 16, 2026
Member
malwilley
left a comment
malwilley
left a comment
There was a problem hiding this comment.
Feel free to merge if you like the wording as-is, just have some thoughts
| <Text> | ||
| {t( | ||
| 'Alerts notify your team. Define who gets paged, when, and how — via Slack, email, PagerDuty, and more.' | ||
| 'Issues created by Monitors trigger Alerts. Alerts define who gets paged, when, and how — via Slack, email, PagerDuty, and more.' |
Member
There was a problem hiding this comment.
This sentence makes me wonder "are there issues which are not created by monitors?" 🤔
could also word this the first sentence this way: Alerts are triggered by issue state changes or Issue state changes will trigger Alerts
Contributor
Author
There was a problem hiding this comment.
"Alerts are triggered when issues are created or updated."
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewrites steps 3 and 4 of the monitors onboarding carousel to more clearly explain that Monitors create Issues, and that Alerts notify teams about those Issues. Previous copy was vague about the role of issue creation in the monitor-to-alert flow.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.