Skip to content

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

Open

Description

@fschwahn

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://public@127.0.0.1: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

Activity

  1. linear-code commented on Nov 16, 2026

    @linear-code
  2. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Nov 16, 2026
  3. sentry-junior commented on Nov 16, 2026

    @sentry-junior
    Contributor

    Reproduced in getsentry/repro#94. Fix: #3210, waiting for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugJunior: reproJunior reproduces this bug and drafts a fixRuby

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions