Update monitor details with state definitions and environment management instructions #11896
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will increase total bundle size by 950 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
|
| description: "Learn how to navigate the Monitor Details page to help you understand your recurring job's overall health." | ||
| --- | ||
|
|
||
| The **Monitor Details** page is where you'll find a daily historical bar chart showing successful, failed, and missed check-ins and a line chart of the runtime average for the job execution. |
There was a problem hiding this comment.
The timeline is here too right?
Also it's actually an Area chat for the durations
| A monitor can have three states: active, muted, and disabled. Only disabled monitors do not count towards your plan's monitor limit. | ||
|
|
||
| - **Active:** The monitor is currently accepting and processing check-ins. New Cron Monitor issues will be created for failed or missed check-ins according to your monitor configuration. | ||
| - **Muted:** The monitor and it's environments are accepting check-ins but will not create any Cron Monitor issues for failed or missed check-ins. This is useful when you want to temporarily disable alerting for a monitor. |
There was a problem hiding this comment.
timeouts too, not sure if you want to include that
|
|
||
| A monitor can have three states: active, muted, and disabled. Only disabled monitors do not count towards your plan's monitor limit. | ||
|
|
||
| - **Active:** The monitor is currently accepting and processing check-ins. New Cron Monitor issues will be created for failed or missed check-ins according to your monitor configuration. | ||
| - **Muted:** The monitor and it's environments are accepting check-ins but will not create any Cron Monitor issues for failed or missed check-ins. This is useful when you want to temporarily disable alerting for a monitor. | ||
| - **Disabled:** The monitor and it's environments are not accepting check-ins, with any check-ins sent to a disabled monitor will be dropped. Disabled monitors do not count towards your plan's monitor limit. | ||
|
|
||
| <Alert level="info" title="Note"> | ||
| The monitor state supercedes the [environment state](#environment-state). If a | ||
| monitor is disabled or muted, so will all environments of it's environments, | ||
| regardless of their individual state. | ||
| </Alert> |
There was a problem hiding this comment.
| A monitor can have three states: active, muted, and disabled. Only disabled monitors do not count towards your plan's monitor limit. | |
| - **Active:** The monitor is currently accepting and processing check-ins. New Cron Monitor issues will be created for failed or missed check-ins according to your monitor configuration. | |
| - **Muted:** The monitor and it's environments are accepting check-ins but will not create any Cron Monitor issues for failed or missed check-ins. This is useful when you want to temporarily disable alerting for a monitor. | |
| - **Disabled:** The monitor and it's environments are not accepting check-ins, with any check-ins sent to a disabled monitor will be dropped. Disabled monitors do not count towards your plan's monitor limit. | |
| <Alert level="info" title="Note"> | |
| The monitor state supercedes the [environment state](#environment-state). If a | |
| monitor is disabled or muted, so will all environments of it's environments, | |
| regardless of their individual state. | |
| </Alert> | |
| A monitor can have three states: active, muted, and disabled. Only disabled monitors do not count towards your plan's monitor limit. | |
| - **Active:** The monitor is accepting and processing check-ins. If a check-in fails or is missed, new Cron Monitor issues will be created based on your monitor's configuration. | |
| - **Muted:** The monitor and its environments accept check-ins, but won't create Cron Monitor issues for failed or missed check-ins. This is useful if you want to temporarily pause alerts without stopping check-ins. | |
| - **Disabled:** The monitor and its environments no longer accept check-ins. Any check-ins sent to a disabled monitor will be ignored. Disabled monitors don't count towards your plan's monitor limit. | |
| <Alert level="info" title="Note"> | |
| The monitor state supersedes the [environment state](#environment-state). If a monitor is disabled or muted, all of its environments will automatically inherit that state, regardless of their individual settings. | |
| </Alert> |
|
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 🥀 |
|
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 🥀 |
|
This issue 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 remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
This issue 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 remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
@gaprl - do you still want to merge this PR? Looks like there are now conflicts, but happy to +1 after it's resolved, since it looks like it already got some +1s on it. |
|
Closing for now. |
Updates the Cron "Monitor Details" page to include different state definitions for the monitor, environments, and how to manage them.
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
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.
EXTRA RESOURCES