getsentry / getsentry/sentry-ruby

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

Ouverte
#2,763 2 commentaires 0 réactions 1 personne assignée Réclamée par @sl0thentr0py Voir sur GitHub
Checks Crons Improvement Ruby
Langage dominant
Ruby
Étoiles
987
Forks
541
Merge moyen
17 h 40 min
PR mergées (30 j)
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_

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.