Events dropped client-side for size are only logged at debug level and not recorded as lost

Aperta Adatta ai principianti
#3,209 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@sentry-junior ci sta già lavorando.

Dal 16/11/2026.

  • #3210 di @sentry-junior — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
76/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
ruby

Direzione di ricerca

Inizia in sentry-ruby/lib/sentry/transport.rb, vicino a Transport#serialize_envelope, e confronta il percorso che scarta gli elementi troppo grandi con la gestione di 413 aggiunta in #2885. Verifica come vengono registrati gli eventi persi e le statistiche degli eventi scartati, quindi aggiungi una visibilità equivalente per questo scarto. Il lavoro è completato quando un elemento troppo grande viene registrato a livello warn e registrato come perso; verifica che la riproduzione riporti un risultato non vuoto per gli eventi scartati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Bug Junior: repro Ruby
Issue Description

When an envelope item is still larger than MAX_SERIALIZED_PAYLOAD_SIZE after Envelope::Item#serialize has removed breadcrumbs and reduced the stacktrace, Transport#serialize_envelope skips it with a log_debug and nothing else:

https://github.com/getsentry/sentry-ruby/blob/master/sentry-ruby/lib/sentry/transport.rb#L77-L82

Since the event is never sent, Relay never sees it, so it doesn't show up in the invalid payload stats either. And unlike the 413 path added in #2885, no client report is recorded. With the SDK logger at the usual info level, the event is lost without any trace.

The size reduction doesn't touch extra or contexts, so a large custom payload is enough to hit this. In our case, a scheduled job reported a list of record ids in extra - the list was about 3 MB, and the event never arrived. We only noticed because we knew a report should arrive, and were confused why none did arrive.

#2381 asked for truncation of custom contexts and was declined in favor of server-side handling, with a pointer to the invalid payload stats. That makes sense for truncation, but these events never reach the server, so the stats can't show them. This issue is only about making the drop visible.

Reproduction Steps
require "logger"
gem "sentry-ruby", "7.2.0"
require "sentry-ruby"

Sentry.init do |config|
  config.dsn = "http://[email protected]:9/1" # nothing listens here; the event is dropped before any request
  config.background_worker_threads = 0
  config.sdk_logger = Logger.new($stdout, level: ENV.fetch("LOG_LEVEL", "info"))
end

Sentry.capture_message("Found records", extra: { ids: (1..200_000).to_a })

puts "discarded events: #{Sentry.get_current_client.transport.instance_variable_get(:@discarded_events).inspect}"
Expected Behavior
  • The drop is logged at warn level, like the 413 response.
  • A lost event is recorded (e.g. record_lost_event(:send_error, item.data_category, num: item.item_count, num_bytes: item.lost_event_byte_size), as in the 413 path), so it shows up in the org's stats.
Actual Behavior

With LOG_LEVEL=info, the script prints only:

discarded events: {}

With LOG_LEVEL=debug, the drop is logged, but still no lost event is recorded:

DEBUG -- sentry: Envelope item [event] is still oversized after size reduction: {event_id: 34, level: 7, timestamp: 22, environment: 13, server_name: 19, modules: 13408, message: 15, user: 2, tags: 2, contexts: 525, extra: 1288904, fingerprint: 2, platform: 6, sdk: 40, type: 7, threads: 1654}
discarded events: {}
Ruby Version

4.0.9

SDK Version

7.2.0

Integration and Its Version

Reproducible with plain sentry-ruby; we noticed it in Rails 8.1 with sentry-rails and sentry-sidekiq 7.2.0.

Sentry Config

No response

Lingua principale
Ruby
Stelle
990
Fork
552
Merge medio
2g 16h
PR unite (30g)
29

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/sentry-ruby

Tutte le issue di getsentry/sentry-ruby

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.