getsentry / getsentry/sentry-ruby

Cron monitors feature sends check-in events without any control of total volume

Open
#2,763 2 comments 0 reactions 1 assignee Claimed by @sl0thentr0py View on GitHub
Checks Crons Improvement Ruby
Dominant language
Ruby
Stars
987
Forks
541
Avg merge
17h 40m
Merged PRs (30d)
19

Description

### Issue Description

sentry-rails sends check-in events for each (scheduled) job instance being run, it leads to errors on Sentry side alerting high volume of incoming check-ins.

### Reproduction Steps

Add job to scheduler with high frequency, at least each minute. Also make job self-enqueueing, so that volume will be even higher.

### Expected Behavior

Check-ins should not fail due to large volume of jobs, sentry-rails should not check-in more frequent than Sentry service allows to.

### Actual Behavior

sentry-rails sends check-ins for each and every call

### Ruby Version

3.4.7

### SDK Version

5.28.0

### Integration and Its Version

GoodJob and Sidekiq

### Sentry Config

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.