update uptime schedule behavior description #11102
Closed
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Bundle ReportChanges will decrease total bundle size by 15 bytes ⬇️
|
evanpurkhiser
approved these changes
Aug 14, 2024
vivianyentran
approved these changes
Aug 26, 2024
| @@ -28,7 +26,7 @@ allowing you to address the underlying connectivity problems. | |||
| ## Notifications | |||
|
|
|||
| An uptime alert continuously monitors the configured URL with the criteria defined above. If a failure is detected, | |||
| a new [uptime issue](/product/issues/issue-details/uptime-issues/) with failed check and related errors details will be created. | |||
| a new [uptime issue](/product/issues/issue-details/uptime-issues/) with failed check and related errors details will be created. To avoid triggering false alerts due to transient issues like network glitches, a new issue is created only after detecting a minimum of three consecutive failures following the initial downtime detection. | |||
There was a problem hiding this comment.
Suggested change
| a new [uptime issue](/product/issues/issue-details/uptime-issues/) with failed check and related errors details will be created. To avoid triggering false alerts due to transient issues like network glitches, a new issue is created only after detecting a minimum of three consecutive failures following the initial downtime detection. | |
| a new [uptime issue](/product/issues/issue-details/uptime-issues/) with the failed check and related error details will be created. To avoid triggering false alerts due to transient issues like network glitches, a new issue is created only after detecting a minimum of three consecutive failures following the initial downtime detection. |
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you add the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
@gaprl let me know if I can help with this in any way :) |
|
Closing in favor of #11420 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Updates uptime's schedule description to once a minute, and adds a note three consecutive failures must be detected before creating a new uptime issue.