getsentry / getsentry/sentry

In-progress check-ins not being sent intermittently with Celery integration

Open
#92,878 7 comments 1 reaction 0 assignees View on GitHub
Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### How do you use Sentry?

Sentry Saas (sentry.io)

### Version

2.29.1

### Steps to Reproduce

We've recently shipped an improvement to the Crons' monitor details page, and noticed that many in-progress check-ins are never being sent across all of our monitors. To reproduce, just set up our automatic detection integration with Celery and go to the monitor details page.

### Expected Result

All check-ins are sending the in-progress check-ins, and not only the completion check-in.

### Actual Result

In-progress check-ins are being missed:

![Image](https://github.com/user-attachments/assets/8acc16ae-c2ac-42d3-8f90-74c30a6fb19b)

Here's some of the impacted monitors:
- [Internal 🔗 ] [monitors-detect-broken-monitor-envs](https://sentry.sentry.io/issues/alerts/rules/crons/sentry/monitors-detect-broken-monitor-envs/details/?statsPeriod=7d)
- [Internal 🔗 ] [fetch-release-registry-data](https://sentry.sentry.io/issues/alerts/rules/crons/sentry/fetch-release-registry-data/details/?statsPeriod=1h)

Contributor guide

Open the contributing guide

Research direction

Start with the automatic detection integration for Celery and trace how in-progress and completion check-ins reach the monitor details page. Compare the two check-in paths and verify that every in-progress check-in is sent for affected monitors, not only the completion check-in.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.