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

Open Beginner friendly
#3,209 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 2 days

@sentry-junior is already working on this.

Since Nov 16, 2026.

  • #3210 by @sentry-junior — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
ruby

Research direction

Start in sentry-ruby/lib/sentry/transport.rb around Transport#serialize_envelope and compare its oversized-item drop path with the 413 handling added in #2885. Check how lost events and discarded event stats are recorded, then add equivalent visibility for this drop. Done means an oversized item is logged at warn level and recorded as lost; verify the reproduction reports a non-empty discarded-events result.

Written by the indexing model from the issue text.

Description

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

Dominant language
Ruby
Stars
990
Forks
552
Avg merge
2d 16h
Merged PRs (30d)
29

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-ruby

All issues in getsentry/sentry-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.