Distillation

Date: July 30, 2026

• 🟡 (15:55) Assistant re-explained how reprocess_only_events_not_in_nodestore flag (d7fcb07bc42, Jul 21 2026) causes event_accepted volume drop: flag added for reprocess tooling checks nodestore.backend.get(node_id) is not None at processors.py:192-196 and returns early, skipping event_accepted.send_robust() at line 313. Kafka is at-least-once so most traffic is already in nodestore, so flag flips cause near-total signal suppression while normal ingest continues
• 🟡 (15:55) Assistant provided 3 fix options ranked by preference: (1) disable flag on consumer fleet running user's processor — intended use of flag is for dedicated reprocess consumers like events-reprocessing, not main events consumer; (2) attach processor to main consumer (without flag) and de-dupe downstream; (3) if processor truly needs all messages, don't rely on event_accepted (overloaded signal — means "saved", not "seen"), subscribe to Kafka directly or patch signal to fire before reprocess check at line ~159 (requires Sentry-side change and discussion with ingest owners)
• 🔴 (15:56) User stated their processor is "only interested in accepted events" — not all traffic. Narrows the fix path to Option 1 (disable flag on consumer running receiver)
• 🟡 (15:56) Grep results (24 matches in repo): flag is wired as a CLI arg --reprocess-only-events-not-in-nodestore at src/sentry/consumers/__init__.py:247, mapped to reprocess_only_events_not_in_nodestore Python attribute. Also documented in .lore.md line 57 (debugging recipe for event_accepted volume drops)
• 🟡 (15:56) Grep results (21 matches): flag flows through src/sentry/ingest/consumer/factory.py (lines 83, 91-99, 132, 155, 207, 215-222, 248) — factory validates mutually exclusive flags reprocess_only_stuck_events and reprocess_only_events_not_in_nodestore (errors at lines 91-94 / 215-218 if both set). Also propagated through simple_event.py:30,74, processors.py:84,192, attachment_event.py:69,98,106
• 🟡 (15:56) Assistant clarified flag is a per-process startup CLI argument, NOT a Sentry option or feature flag. Verified via src/sentry/consumers/__init__.py:247. Verification commands provided: ps aux | grep -E "events\.ingest|events\.reprocessing" | grep -o "reprocess-only-events-not-in-nodestore\|reprocess-only-stuck-events" and ps -ef --forest | grep -i 'sentry run\|consumer'
• 🟡 (15:56) Assistant identified the consumer class likely running user's processor as events.ingest-consumer. If --reprocess-only-events-not-in-nodestore is found on that process, drop it and restart consumer to restore event_accepted signal emission
• 🟡 (15:56) Test files referencing flag: tests/sentry/processing/backpressure/test_checking.py:102, tests/sentry/ingest/ingest_consumer/test_ingest_consumer_kafka.py:228, tests/sentry/ingest/ingest_consumer/test_dlq.py:74 — all explicitly set reprocess_only_events_not_in_nodestore=False