getsentry / getsentry/sentry-ruby

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

Offen
#2,763 2 Kommentare 0 Reaktionen 1 zugewiesene Person Beansprucht von @sl0thentr0py Auf GitHub ansehen
Checks Crons Improvement Ruby
Vorherrschende Sprache
Ruby
Sterne
987
Forks
541
Ø Merge
17 Std. 40 Min.
Gemergte PRs (30 T.)
19

Beschreibung

### 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_

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.