Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cron monitor: Failure and recovery thresholds config #1919

Closed
Tracked by #43 ...
szokeasaurusrex opened this issue Jan 29, 2024 · 0 comments · Fixed by #1922
Closed
Tracked by #43 ...

Cron monitor: Failure and recovery thresholds config #1919

szokeasaurusrex opened this issue Jan 29, 2024 · 0 comments · Fixed by #1922
Assignees

Comments

@szokeasaurusrex
Copy link
Member

szokeasaurusrex commented Jan 29, 2024

See getsentry/team-sdks#43

@szokeasaurusrex szokeasaurusrex transferred this issue from getsentry/team-sdks Jan 29, 2024
@szokeasaurusrex szokeasaurusrex changed the title Sentry CLI Cron monitor: Failure and recovery thresholds config Jan 29, 2024
@szokeasaurusrex szokeasaurusrex self-assigned this Jan 29, 2024
szokeasaurusrex added a commit to getsentry/sentry-rust that referenced this issue Jan 29, 2024
szokeasaurusrex added a commit that referenced this issue Jan 30, 2024
This PR adds the `--failure-issue-threshold` and `--recovery-threshold` command line arguments. These control the number of consecutive failed cron checkins that trigger issue creation, and the number of consecutive successful cron checkins that trigger issue resolution, respectively.

Fixes GH-1919
szokeasaurusrex added a commit that referenced this issue Jan 30, 2024
This PR adds the --failure-issue-threshold and --recovery-threshold command line arguments. These control the number of consecutive failed cron checkins that trigger issue creation, and the number of consecutive successful cron checkins that trigger issue resolution, respectively.

Fixes GH-1919
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant